By the time you're reading this, if all has gone well, my blog will be serving itself from Amazon S3. (Disclaimer: I work for Amazon, but my opinions are my own and are not intended to represent Amazon's. Although I'm pretty sure we agree that AWS is awesome.) Hopefully, this will be a more scalable, secure, and convenient way for me to blog. Why am I making this leap, you ask? I will concede that if you think my design just took several steps backwards took several steps backwards. Well, there are a couple of reasons. Pull up a chair.
My personal website (and blog) have been hosted on Dreamhost for the past ~5 years. However, they've screwed up a bunch of times in the past year, and I'm not super comfortable with them hosting my things. I'm also looking forward to ditching my old hosted WordPress install. I don't use it for any of the things that it's good at (I disabled comments, have only a few pages, and don't need multiple editors, to name a few...), and it's not https, so I have to be careful about where I log on, for fear of sending my password as plaintext. (And no, I don't use that password for anything else important, but still, http-only is bad.) It's also not that convenient, because I can only access draft blog posts when I have internet access, which is a little silly.
Anyway, enter S3. A few months ago, I started playing around with Jekyll and S3 web hosting. However, I'm bad at making things look pretty, so I didn't pull the trigger on the site since I wasn't happy with the design. (There are also some rough Jekyll edges that I need to round off.) Finally, I decided that I just needed to do it, so here I am, waiting for the DNS to propagate. Hopefully I will have a Jekyll post up soon. (And my source on GitHub!)