Contents

migration to octopress

Contents

I’ll admit it. I’ve been ignoring this blog for a while. Recently, over lunch, my friends started talked about their moribund blogs and the basic security threat they implied. My friend Sean said that he’d migrated to octopress based on a blog post. Given that we had all been running various versions of wordpress, it seemed like a good idea to investigate some other, less risky solution. I had sort of kept up with wordpress upgrades, but didn’t make the leap to the 3.x series. I actually tried it recently, and discovered that my PHP version on the host wasn’t up to snuff.

So, I’ve decided to take the plunge as well. I haven’t yet decided to move my blog to github pages, but I have done some work to get octopress working on my existing host. This is the default octopress theme. I’m going to leave it like that for a while, because a) it works and looks fine, and b) I’m not entirely sure how to change it. As part of the migration, all of my posts were transcoded into Markdown (in some cases, back into Markdown, but the majority were straight html.) As such, some of the formatting is broken. I plan to fix them as time goes on.

Octopress has the advantage of just generating static HTML sites (which you then move to the host via rsync or git.) This makes me much happier from a security standpoint. On the other hand, I now have to have Octopress installed on any machine that I want to be able to post from.

Since comments were actually useful on my site (although I was very remiss in moderating them), I’ve moved them to disqus, as octopress can’t handle them in line.