1136790 - Production deployment

Status: RESOLVED FIXED

(Firefox OS Graveyard :: Gaia::Bugzilla Lite, defect)

Description

[Dale Harvey (:daleharvey)]

This is currently on a personal repo with no official hosting etc

I can put the mpl on it and switch it to a gaia repo, however I do not want / think it should be inside mozilla-b2g/gaia, this is going to be a hosted web application with no shared dependencies. 

Vivien, given we are looking to do this to more applications for v3, is there any plans / ideas in mind about how best to do this. There is https://github.com/fxos/ being experimented with however the main question would be how to we handle the IT related things / hosting?

Comment 1

[Dale Harvey (:daleharvey)]

CC'ing Kevin as well as he mentioned something about this

Comment 2

[Dale Harvey (:daleharvey)]

Clearing needinfo, hosting on heroku for now

Comment 3

[Dale Harvey (:daleharvey)]

To clarify from the call, the domains needing an ssl cert currently are:

bzlite.com
v1.bzlite.com
staging.bzlite.com

Comment 4

[Dale Harvey (:daleharvey)]

Hey Richard

Have you installed SSL on to heroku before? wondering if you could guide me a little since I have only done it on my own host once before and the process is looking extremely different. I dont see any mention of the chained root certificate etc in https://devcenter.heroku.com/articles/ssl-endpoint

Cheers
Dale

Comment 5

[:Atoll]

I have not. I did some research and, basically, where those instructions say 'server.crt', they really mean 'a concatenated file containing both your server certificate and any chained intermediates'.

So for Heroku, you would apparently run:

$ heroku addons:create ssl:endpoint
$ cat your_server.crt intermediate.crt > for_heroku.crt
$ heroku certs:add for_heroku.crt your_server.key

And then wait for it to provision:

$ heroku certs:info

And then add the domain to your app:

$ heroku domains:add your.server

If you can get as far as the certs:info output showing the certificate, I can certainly validate the output at that stage to make sure it is valid SSL and so forth. Let me know?

Comment 6

[Dale Harvey (:daleharvey)]

https://www.bzlite.com/ is live, thanks so much

Comment 7

[Dale Harvey (:daleharvey)]

Actually need to get the manifest pointing to https

Comment 8

[Dale Harvey (:daleharvey)]

Attachment: https://github.com/mozilla-b2g/bzlite/pull/16

Hey Doug, once this is in we can/should switch to v2 in spark

Comment 9

[Doug Sherk (:drs) (inactive)]

Comment on attachment 8620399 [details] [review]
https://github.com/mozilla-b2g/bzlite/pull/16

https://bzlite.com seems dead for me. I used http://bzlite.com instead. Dale and I agreed on IRC to wait on this review until https://bzlite.com works.

This is a pretty trivial patch, so I figured that I would use this time to do some testing on the whole experience. Here are some other issues that I've found. I didn't file any bugs for them because I'm not sure whether or not they're intentional or Dale/Jacqueline want to take them.

* Problem: The "Profile" page has nothing but a logout button.
* Suggestion: The comment threads should have the most recent comment at the top, for a more mobile-friendly approach. Maybe we could guard the arrangement behind an @media query in the future.
* Suggestion: Bug section tabs ("Comments", "Details", "Attachments") should go at the top of the screen.
* Suggestion: "Take Bug" seems like it's unlikely to see much use. Chances are that you're not going to be assigning bugs to yourself when filing them using BzLite. I could definitely be wrong here though.
* Suggestion: Bug headers could include part of the summary instead of just the number.
* Suggestion: On the main bug list view, include a tag "You Reported" or some such, indicating that you reported the bug.
* Suggestion: Include recently resolved bugs at the top of the bug list. Move them down to the bottom once you've viewed the resolution.

Comment 10

[Dale Harvey (:daleharvey)]

We have a fair amount of these on the backlog as improvements to bzlite, not all of them exactly as suggested but along the same lines

Comment 11

[Dale Harvey (:daleharvey)]

So fixing https://bzlite.com is tricker, either need to switch domain provider or host so I have switched the manifest to https://www.bzlite.com and filed http://www.bzlite.com/bug/1173726 for fixing https://bzlite.com

Comment 12

[Dale Harvey (:daleharvey)]

pinging for review Doug, cheers

Comment 13

[Dale Harvey (:daleharvey)]

Thanks, merged in https://github.com/mozilla-b2g/bzlite/commit/ed492677b3bdb080ded81a26512ff084535453f5