static void

Cloudflare and Github Pages

Published Monday 14 November 2016

After 7 years on GoDaddy, has moved on to Github Pages behind Cloudflare. It's pretty easy, and both services are free.

The GoDaddy hosting (the cheapest level for was on IIS7 (so Windows Server 2008) with maximum of .net 4.0. The blog was the ancient dasBlog. There are better hosting companies, but it's not cheap for personal site, and overkill for a blog. Github Pages is free static hosting, backed by a Github repository. Developers need to be on Github anyway, so why not add your blog to it? There's no dynamic code, but you can use Jekyll as a static site generator. It was simple to convert the dasBlog blog entries into plain html. At that point Jekyll itself became overkill. The Jekyll-redirect-from gem creates an html page with a browser-redirect (meta-refresh/javascript), so I just wrote a quick script to generate some identical redirect htmls and pushed those.

Github Pages are otherwise normal git repositories (git push, accept pull requests and github issues).

Cloudflare sits in front of a site, acting as a content delivery network and DDoS firewall. Acting as a reverse proxy, they can even provide https for your site (although it's not end-to-end security at the free level). According to their analytics, I saved 6% in bandwidth due to their caching, and 68 threats over the last week (mostly US and Ukraine). One of the reasons I stripped back the asp to html was the number of probing attacks I used to see in my logs, trying to break in via /admin and non-existent urls. With static code, it's (mostly) bullet-proof. Despite not publishing any https links, 3% of traffic is already SSL.

Previously: Dotnet Core Class Libraries (22 May 2016)