It took a while, but it has finally become obvious to me that I need to spend less time making my blog work and more time doing interesting things to blog about. In other words, I need a blog that “just works”. WordPress. The two complicating factors are that it needs play nice with nginx and postgres. The solution is to use FastCGI and the PostgreSQL for Wordpress (pg4wp) plugin.
So after my brief stint using Hyde I’ve decided that its just not quite right for me. That being said I still hoped to avoid the A, M and P pillars of the LAMP stack, so I wasn’t going to just roll out a Wordpress or Drupal instance. I investigated a few existing Django blog solutions but in the end decided to just make my own. So here it is. Its nowhere near done, but as I work I keep finding topics to blog about, so I finally decided to just get something online so at least I can use it in the process.
Like many in the open source community, I’ve developed a bit of an addiction to git. I use git for keeping track of class notes, homework, this blog, nearly everything we do on the OSU Open Source Lab Systems team and, of course, coding. I have hosted a number of repositories (mostly for long dead programming projects on GitHub but while it has a lot of great features, sometimes I just want a level of control that github just doesn’t offer.
I’ve decided to give blogging another shot. Since I only have 360MB of RAM on my VPS, and plan to use it for a number of other services, I want to keep resource use to a minimum. I’ve been playing with nginx and love it, but what to use for the blog? I’m not going to run MySQL just for a blog, which rules out Wordpress and Drupal. I really don’t like SQLite.