1176488 - Set up custom <TBD>.mozilla.org domains for the Treeherder Heroku apps

Status: RESOLVED DUPLICATE of bug 1277268

(Tree Management :: Treeherder: Infrastructure, defect, P2)

Description

[Ed Morley [:emorley]]

eg:
https://devcenter.heroku.com/articles/custom-domains

We'll need to use the SSL Endpoint addon too:
https://devcenter.heroku.com/articles/ssl-endpoint

...and generate keys etc.

We'll want to get this all sorted a fair amount before we actually need webops to make the changes to the treeherder.{mozilla,allizom}.org DNS.

Comment 1

[Ed Morley [:emorley]]

We'll need to:

1) Get webops to give us a certificate+private key for <subdomain>.mozilla.org
2) $ heroku addons:create ssl:endpoint
3) $ heroku certs:add server.crt server.key
4) Verify with `heroku certs` and `heroku certs:info`. (For more info see: https://devcenter.heroku.com/articles/ssl-endpoint#endpoint-details).
5) $ heroku domains:add <subdomain>.mozilla.org
6) Find out the ssl CNAME target using `heroku domains` (https://devcenter.heroku.com/articles/custom-domains#view-existing-domains)
7) Get the DNS for <subdomain>.mozilla.org updated to point to the ssl CNAME target from step #6.
8) Verify SSL using the steps at: https://devcenter.heroku.com/articles/ssl-endpoint#testing-ssl

Comment 2

[Ed Morley [:emorley]]

Regarding the security of private keys uploaded to Heroku, bug 1191075 verified they are safe.

Comment 3

[Ed Morley [:emorley]]

This has been split into two parts:
1) Add the certs/keys in advance to the Heroku SSL endpoint addon -> bug 1277268
2) Making the DNS changes -> will be a new bug filed as a dep of bug 1277304