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 188.8.131.52 3600 www CNAME srihash.org 86400
François, Would it be easier for you to host this on heroku?
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.
:francois sorry for the delay on this, I have been out sick. I will rich out to you on IRC today.
I have created an app on herkou and have sent an account request to :francois
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
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.
Hm, not sure how I took it over in the first place, but I've just transferred it back to mozillacorporation.
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 @.
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
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
Everything looks good, thanks Ryan!
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.