1024180 - Deploy Loop-Client 0.2.0 to Production

Status: VERIFIED FIXED

(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task, P1)

Comment 1

[James Bonacci [:jbonacci]]

I assume this will include support for https://call.mozilla.com - see bug 1021891

Comment 2

[Benson Wong [:mostlygeek]]

This new code will be served at the https://call.mozilla.com. This won't affect the current production setup but when 1024222 is deployed the new call.mozilla.com will be used.

Comment 3

[Benson Wong [:mostlygeek]]

note: holding off on this deploy for now as it doesn't make sense to deploy without a new production worthy loop-server.

Comment 4

[James Bonacci [:jbonacci]]

https://github.com/mozilla/loop-client/tree/0.2.0

Comment 5

[James Bonacci [:jbonacci]]

Still working out the bugs/issues. When this is all done, you should have access to the following:
https://loop.services.mozilla.com running 0.9.2 code

https://call.mozilla.com running 0.2.0 code

Sorry for the delays...

Comment 6

[James Bonacci [:jbonacci]]

Wrong bug...
sigh....

Ignore previous comment

Comment 7

[James Bonacci [:jbonacci]]

:bobm finally got this working. Here is what I see...

Browser: https://call.mozilla.com
Loop
Welcome to the Loop web client.

Browser: https://call.mozilla.com/config.js
var loop = loop || {};
loop.config = {serverUrl: 'https://loop.services.mozilla.com'};

curl -I https://call.mozilla.com/
HTTP/1.1 200 OK
Accept-Ranges: bytes
Content-length: 2010
Content-Type: text/html
Date: Thu, 24 Jul 2014 23:21:36 GMT
ETag: "53d15681-7da"
Last-Modified: Thu, 24 Jul 2014 18:54:57 GMT
Vary: Accept-Encoding
Connection: keep-alive

Comment 8

[James Bonacci [:jbonacci]]

No red flags from the QA teams. I call that a win.