neutrino.js.org

[edmorley]

Since we're switching from GitHub pages to Netlify, for all the auto-deployment and PR preview goodness.

See:
neutrinojs/neutrino#891

• There is reasonable content on the page (see: No Content)
• I have read and accepted the Terms and Conditions

cc @eliperelman

[indus]

@eliperelman I took your "Looks great" from neutrinojs/neutrino#891 (review) as an indication that you as the initial requester of the subdomain support the change and processed this change request of @edmorley.

I've made the change in JS.ORGs zonefile but something looks misconfigure (in netlify ?). I get a warning about the SSL certificate. Maybe we should use Cloudflares "Universal SSL" (requires removing ````//noCF``` comment in the PR).

[edmorley]

@indus thank you for making the change :-)

Netlify has integrated Let's Encrypt support, which I was hoping would kick in automatically - though it appears that they only try to add a custom domain to an existing cert when it's first added to the custom domains list - and not when the DNS is finally updated to match. Removing and re-adding the custom domain entry triggered the cert issuance - https://neutrino.js.org/ works for me now. (It seems like there isn't a way to make it zero downtime when using //noCF.)

Thank you for your help!

[edmorley]

(In case it helps anyone else in the future)

Ah though https://www.netlify.com/docs/ssl/#troubleshooting says:

3. If your site is configured to go through another service (ex: using CloudFlare “acceleration and protection”, or similar), you’ll need to disable that routing before trying to provision a certificate in our UI, so Netlify can handle SSL termination.

So it seems it's just a chicken-and-egg situation for which a downtime is always unavoidable.

[indus]

Welcoem back https://neutrino.js.org