https://help.github.com/articles/quick-start-setting-up-a-custom-domain/
I would also recommend Cloudflare approach (I work there). Makes it pretty convenient to enforce things like dns and caching. You can actually have cloudflare talk to github over https using the “Full” but not the “Full (strict)” setting. This makes sure there is TLS at the origin connection but does not verify the certificates.
I can't seem to find the documentation for custom domains on GitHub Pages.On the other hand, CloudFlare doesn't support custom reverse proxy URLs,but rather proxies the Host request header directly to the server. Wecan't use it in front GitHub Pages unless we are willing to have itreverse proxy the unsecured HTTP origin. Granted this is better havingvisitors visit our HTTP site, as CloudFlare and GitHub are likely bothon the same Internet exchanges and should be less prune to MITM attacks,but at the end of the day it is still delusional HTTPS.HowardJorrit Poelen:Cool, sounds like there's plenty of options.
Would anyone on the list like to set this up? I'd be able to do it, but
it might be a while.
The repo is at https://github.com/buildyourowninternet/buildyourowninte
rnet.github.io .
_______________________________________________mesh mailing listmesh@lists.sudoroom.orghttps://sudoroom.org/lists/listinfo/mesh