arch bash cakephp conf dauth devops drupal foss git golang information age life linux lua mail monitoring music mysql n900 netlog openstack perf photos php productivity python thesis travel uzbl vimeo web2.0

Migrating blogs from Drupal to Pyblosxom

pyblosxom is a pretty cool blogging platform written in python.
Like many of the modern minimal blog engines it works with plaintext files only (no database), has a relatively small codebase, supports many plugins (like markdown support), is written in a proper scripting language, has a simple and clean file structure, is seo-friendly, and so on.
The one feature that sets it apart from other minimal blog engines is that it supports comments, and doesn't just rely on an external service like disqus, but stores comments as plaintext files as well.
Some features seem a bit overengineered (like, multiple possible locations to store themes (known as "flavours") and templates; I'm a fan of convention over configuration and keeping things simple), but discussing this with the maintainer revealed this is because pyblosxom is meant as a reimplementation of the original perl-based bloxsom project. Over time features could be simplified and/or redesigned.
So I plan to migrate this blog from drupal to pyblosxom.
To do this, I'm building the tool drupal-to-pyblosxom.
The goal is to convert posts, associated metadata (publish time, tags) and comments from the drupal database to pyblosxom files. Source code display should be converted too (merely a matter of converting between different plugin conventions), and images shown should be downloaded. Currently I'm about halfway, if there's anyone out there with a similar use case, help is welcome ;)


Out of interest, what was your reasoning not to outsource commenting to something like Disqus? If your requirement wasn't so strict, there are many other other good "static website generators".

I'm just hesitant to rely on 3rd parties.
I consider comments to be part of the blog, so I want to own a copy of the comments data and store them alongside the posts.
I saw somewhere you can get an export of your comments from discus at any time. Maybe you can even get your comment when it is posted, I don't know. If there was a lightweight blog thingie that would use discus but also would make sure you get a copy of the comment as a file at the same time, *and* serve it up when disqus is unavailable, that would be pretty useful and might change my mind.

I think there's definitely a good use (and hence, a "need") for more interoptability between blogs and giving users more control/oversight over their comments (and followups) but that's something I want - as a user - to control myself, and I know I'm not the only one thinking this way.
As long as blogs have rss feeds for comments (per thread), I can have it added to my local feed list and be informed automatically on followups





What is the first name of the guy blogging here?

This comment form is pretty crude. Make sure mandatory fields are entered correctly.
Basic html tags (a,i,b, etc) are allowed, others are sanitized