The blog has now fully moved over to Movable Type, including all past articles and their comments. It took a bit of Perl, Python and mucking with SQL, but now the transfer is complete.
The reason for the move is that the app I was using, RapidWeaver, was beginning to introduce a bit too much inertia to the blogging process. And one thing I know about myself: if something isn’t dead simple, even after months of being away from it, I’ll avoid it forever.
I write these blog posts using ecto now, which couldn’t be easier. There’s no separate publishing step, it’s like writing and sending an e-mail.
I actually liked the way WordPress looks a bit more, but Movable Type supports PostgreSQL, which is what ever other service on this server uses. And for some reason MT’s XML-RPC script doesn’t work with FastCGI and Apache, which is something I guess I can live with.
Any rationale behind Movable Type apart from Postgres support? I’ve been making similar choice for my blogs last year and settled on Serendipity (giving some consideration to Habari) - as Movable Type seemed to me to be too complicated to setup….
It was mostly the PostgreSQL support, actually, and that I’d seen it mentioned in various places around the web. I think it could use some simpler widgets – it seems WordPress is superior in that category – but otherwise I haven’t found it complicated to use at all.
In fact, installation was perhaps the smoothest I’ve seen yet for a Perl or PHP server app. When I recall the pain involved with setting up Gallery or phpbb2, MT veritably shone by comparison.
Perhaps it helped that I installed it on a CentOS box that had a repo link to rpmforge, so nearly every dependency during the install was downloaded and working in seconds.