Now that I can build my blog via continuous integration, I want to push the digital envelope and go to full continuous deployment.

GitHub Pages

Apparently, the most common way to deploy Jekyll applications is via GitHub Pages. Put your Jekyll configuration in GitHub and magically you can have your own blog complete with subdomain and automated deployment.

Well that sounds perfect! It’s simple. Lots of people are doing it. Why shouldn’t I?

And then I ran across this article:

F%#ck Github Pages for my Jekyll blog. Why I decided to use Digital Ocean instead?

Welp, looks like I’m going to probably run into just as many problems as this poor folk had. Better look for an alternative.

Digital Ocean

This wasn’t the first time I heard of Digital Ocean. A bunch of my friends use it for things like Mumble servers, Wedding websites, and more. Honestly, I’ve been looking for a good reason to try something other than Rackspace (which I’ve been using for the last 5+ years).

Using Digital Ocean, I can get my own server (aka “droplet”), run a web service on it, deploy my “built” html to it, and then be able to browse my new blog.

Felt straight forward and very familiar.

But as I perused the distributions and applications made available to me, each of the options felt far too complex for my simple static HTML.

Do I pick the comfortable Ubuntu server where I still need to manage the accounts, security, updates, etc? What about the Docker application? I could build all my sites as simple Docker containers, deploy them to this server, and use some fancy Nginx configuration to route between them.

All of this made me very uncomfortable. I felt like nothing has changed since I last did this 5+ years ago.