Migrate from Openshift v2 by end of September/December about mathdown HOT 9 CLOSED

We heard your concerns about the OpenShift Online v2 sunset and we’d like to give you some additional time to migrate to OpenShift Online Next Generation. We’re extending access for paying users of the OpenShift Online v2 platform until December 31, 2017.

However that's only paying users, in line with my usual pretending ;-) that others might want to fork/deploy this, I better have it working by EOSep.

from mathdown.

Turns out I'm on Bronze not Silver. I'm paying on bronze for more CPUs & disk, but got email:

After September 30th, 2017, applications created in Free and Bronze accounts in Red Hat OpenShift Online 2 will be removed.

Had too much work, Openshift 3 doesn't Just Work (builds get stuck, "Failed to push the image to the registry"...). Will have more time for Mathdown in couple weeks.
=> For now moving to Heroku.

from mathdown.

Flipped [www.]mathdown.com DNS to heroku.
Configured Heroku to use same certs for the 4 domains.

• https://prod-heroku.mathdown.com/ CNAME alias has bad TLS.
  (Had good when I tried auto certs, but avoiding auto certs as they won't work until I flip DNS)
  • https://mathdown.herokuapp.com is fine
• https://staging-heroku.mathdown.com/ CNAME has bad TLS.
  • https://mathdown-staging.herokuapp.com is fine

Getting CI to finally pass (#173) so I'm able to safely deploy newer versions (not together with switching, RHcloud and Heroku prod both run same ancient version, but want the ability.)

from mathdown.

Flipped [www.]mathdown.net DNS to Heroku too.

from mathdown.

• TODO: Backup RHcloud app (logs)

from mathdown.

I'm told server.coffee might be a problem, I need server.js.

from mathdown.

Downloaded logs from openshift 2 online, nothing interesting.
Deleted prod-mathdown app, to stop paying.

from mathdown.

Great timing. Heroku is having troubles this morning, mathdown has been down for over a hour now.
Heroku logs show only their router complaining it can't reach the app:

2017-10-31T07:35:20.698924+00:00 heroku[router]: at=error code=H19 desc="Backend connection timeout" method=GET path="/" host=mathdown.herokuapp.com request_id=f75ca5ee-6a81-4d29-be48-f71f622dc45b fwd="69.162.124.229" dyno=web.1 connect=5001ms service= status=503 bytes= protocol=https
2017-10-31T07:35:25.709067+00:00 heroku[router]: at=error code=H19 desc="Backend connection timeout" method=GET path="/" host=mathdown.com request_id=3bd3b4f5-9368-44c7-9a82-aaa40b8696a0 fwd="69.162.124.231" dyno=web.1 connect=5001ms service= status=503 bytes= protocol=https
2017-10-31T07:35:34.764862+00:00 heroku[router]: at=error code=H19 desc="Backend connection timeout" method=GET path="/" host=www.mathdown.net request_id=971068e5-5877-4e90-8cca-2c154006035b fwd="69.162.124.231" dyno=web.1 connect=5000ms service= status=503 bytes= protocol=https
2017-10-31T07:35:38.554683+00:00 heroku[router]: at=error code=H19 desc="Backend connection timeout" method=GET path="/" host=www.mathdown.com request_id=6bf6265f-5871-4ccd-ab46-f2a0c28373af fwd="69.162.124.231" dyno=web.1 connect=5001ms service= status=503 bytes= protocol=https

https://status.heroku.com/ said they have problems with dynos, builds and deployments, and attempts to restart the say Heroku temporarily disabled this.

=> Trying to fall over DNS to https://staging-mathdown.rhcloud.com which is still alive.
Need to deploy domains & certs to that app.
rhc-set-certs.sh staging mathdown certs/mathdown.net/privkey.pem worked 👍

from mathdown.

works for now. looking into static hosting alternatives with custom domain TLS (surge.sh, static.land, ...).

P.S. also considering switching to "chat ops" eg. gitter to have less production-related spam in github issues.

from mathdown.