Enable HTTPS

[mathiasbynens]

Making the website available over HTTPS would make it possible to add a service worker which could then be used to fix https://twitter.com/mbrochh/status/715135779136086017.

Since you seem to be using GitHub Pages, I guess enabling Cloudflare is the simplest way to set up HTTPS.

[janl]

I think this is simple enough to do in AppCache, as the previous site: b3b1dd7

That way we avoid more infra overhead at this point.

[mathiasbynens]

AppCache is going away, though.

• Firefox is dropping it entirely.
• Chromium is working on deprecating-then-removing it over insecure origins such as http://offlinefirst.org.

Adding a service worker is the only future-proof way of adding this functionality.

[janl]

sure, but right now, AppCache is the only thing that works and everywhere, and we don’t have to set up TLS for it, so I think it’s a clear win.

[janl]

implementation here: #12

[gr2m]

but let’s leave this open, would have https, so we can host Service Worker things ™️ Also appcache can still be used as fallback to ServiceWorker

[afknapping]

i am currently testing moving my own github-pages-site-with-custom-domain over to gitlab since they support SSL/TLS with custom domains via Let's Encrypt.

can let you know how that works out if interested (well, and if moving to gitlab is an option at all :)

[terichadbourne]

@gr2m @kidfribble Wondering if we can circle back to enabling HTTPS both on offlinefirst.org and on the new offline.camp when we get that in place?

[gr2m]

That should fairly easy now: https://github.blog/2018-05-01-github-pages-custom-domains-https/

Important part:

If you are using A records, you must update your site's DNS records with new IP addresses. Please see our guide to setting up your custom domain with Pages and update any A records you might have set.

whoever owns offlinefirst.org has to update the A record, then we can set the switch to enforce SSL on the domain

[terichadbourne]

The other issue that needs updating by the owner is this, which sounds related in the fix:

The page build completed successfully, but returned the following warning for the `gh-pages` branch:

The custom domain for your GitHub Pages site is pointed at an outdated IP address. You must update your site's DNS records if you'd like it to be available via your custom domain. For more information, see https://help.github.com/en/articles/using-a-custom-domain-with-github-pages.

For information on troubleshooting Jekyll see:

  https://help.github.com/articles/troubleshooting-jekyll-builds

If you have any questions you can contact us by replying to this email.

@gr2m told me earlier when I showed him that:
"not sure who owns offlienfirst.org right now, looks like it is on IWANTMYNAME.NET? The DNS entry needs to be updated to point on a new IP"

@kidfribble Have you already figured out who has it registered right now? @janl perhaps?