Status

RESOLVED FIXED
3 years ago
19 days ago

People

(Reporter: francois, Assigned: rwatson)

Tracking

Details

(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/1805] )

(Reporter)

Description

3 years ago
I'd like to get hosting for https://srihash.org which is an evangelism website for a feature that is landing in Firefox dev edition next Monday (bug 1205448).

It's a pretty simple node.js backend and the code is at https://github.com/mozilla/srihash.org

The domain is currently owned by me and so I have filed a transfer bug for it (bug 1206286).

DNS-wise, all it has is this:

  @    A      192.81.133.89   3600
  www  CNAME  srihash.org    86400

Updated

3 years ago
Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/1805]
François,

Would it be easier for you to host this on heroku?
(Assignee)

Updated

3 years ago
Assignee: server-ops-webops → rwatson
(Reporter)

Comment 2

3 years ago
I've never used Heroku before, but I'm sure that would work.

What do I have to do to move it there?
Ryan will be able to assist you with that.
(Assignee)

Comment 4

3 years ago
:francois sorry for the delay on this, I have been out sick. I will rich out to you on IRC today.
(Assignee)

Comment 5

3 years ago
I have created an app on herkou and have sent an account request to :francois
(Reporter)

Comment 6

3 years ago
The app is live at https://srihash.herokuapp.com and is setup for auto-deploy off of https://github.com/mozilla/srihash.org

Ryan, if you could please:

1. change to a permanent app tier
2. provision and install a new srihash.org TLS cert
3. point DNS to Heroku
(Assignee)

Comment 7

3 years ago
Hi Francois,

It looks like you were able to set it to permanent tier, but in doing the transfer to you looks like it's no long under the "mozillacorporation" which means we can't provision any of the other stuff.
Can you transfer the ownership back to Mozilla and I can continue with the rest.

I have purchased the cert and can get the rest of this done today.
(Reporter)

Comment 8

3 years ago
Hm, not sure how I took it over in the first place, but I've just transferred it back to mozillacorporation.
(Assignee)

Comment 9

3 years ago
certs$ heroku certs:add www_srihash_org.crt www_srihash_org.key --app srihash
Resolving trust chain... done
Adding SSL Endpoint to srihash... done
srihash now served by yamanashi-5422.herokussl.com
Certificate details:
Common Name(s): srihash.org
                www.srihash.org

Expires At:     2017-10-10 12:00 UTC
Issuer:         /C=US/ST=California/L=Mountain View/O=Mozilla Corporation/CN=www.srihash.org
Starts At:      2015-10-06 00:00 UTC
Subject:        /C=US/ST=California/L=Mountain View/O=Mozilla Corporation/CN=www.srihash.org
SSL certificate is verified by a root authority.
updating Heroku CLI...done. Updated to 3.42.15

This then gave us the SSL DNS:
yamanashi-5422.herokussl.com

Currently I am unable to point srihash.org > yamanashi-5422.herokussl.com due to limitations in CNAME for @ domains.

www.srihash.org is currently pointed to heroku.. we are trying to work out a good solution for the @.
(Assignee)

Comment 10

3 years ago
Bit of a nasty hack, but I have a re-direct working for now:
I did srihash.org > static.zlb.phx.mozilla.net (then did SSL mapping on the load balancer) > redirect via apache/static server > www.srihash.org
(Assignee)

Comment 11

3 years ago
So I believe we are done here? 
If you need anything else feel free to re-open or file a new bug.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
(Reporter)

Comment 12

3 years ago
Everything looks good, thanks Ryan!

Updated

19 days ago
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.