Closed cben closed 6 years ago
cben
commented
6 years ago 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.
cben
commented
6 years ago 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.
cben
commented
6 years ago Flipped [www.]mathdown.com DNS to heroku. Configured Heroku to use same certs for the 4 domains.
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.)
cben
commented
6 years ago Flipped [www.]mathdown.net DNS to Heroku too.
cben
commented
6 years ago cben
commented
6 years ago I'm told server.coffee might be a problem, I need server.js.
cben
commented
6 years ago Downloaded logs from openshift 2 online, nothing interesting.
Deleted prod-mathdown app, to stop paying.
cben
commented
6 years ago 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=httpshttps://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 :+1:
cben
commented
6 years ago 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.
The old openshift online is shutting down, must migrate to the new kubernetes-based openshift online (the platform is not so new – https://www.openshift.org/ — but RedHat just recently made it available as hosted PaaS.) https://blog.openshift.com/migrate-to-v3-v2-eol/ https://www.openshift.com/get-started/migrate.html
Do I still want to run on Openshift / Heroku?
I don't have enough time to maintain mathdown :-( See #172 for my plans. I'd like to go back to static hosting.
Anyway, I happen to work in RedHat on Openshift-related things, so I feel I ought to make it work even I won't stay on it :-)