the future of pyblosxom

This site runs on Pyblosx­om, a weird but inter­est­ing weblog sys­tem writ­ten in Python. Pyblosx­om has the dual ben­e­fits of being very light­weight and extreme­ly cus­tomiz­able. Instead of using a SQL data­base, it stores entries and com­ments in a filesys­tem tree, which is very con­ve­nient for peo­ple who pre­fer a com­mand line to a Web inter­face (me). When I select­ed it in ear­ly 2008, it was still being active­ly devel­oped. It also gave me a good excuse to learn Python, which I have done with mod­est suc­cess.

Per­for­mance and reli­a­bil­i­ty prob­lems with my cur­rent serv­er have led me to want to move this site to a faster vir­tu­al serv­er “in the cloud.” Nat­u­ral­ly, I would install the lat­est ver­sion of Pyblosx­om on said machine, right? Well… For a few months I’ve been test­ing pyblosx­om 1.5rc2, the fruit of two years of spo­radic devel­op­ment by the 3 oth­er peo­ple who actu­al­ly use this soft­ware. Because some back-end redesign neces­si­tat­ed many changes to my Scot­tos­phere mod­i­fi­ca­tions, it took a while to get it con­fig­ured again. And indeed, my non-pub­lic stag­ing serv­er is now about 100 times faster than the cur­rent site. But, to my great frus­tra­tion, I still can’t get com­ments to work prop­er­ly with Ajax. It has become a huge waste of time to debug, and I’m ready to throw in the tow­el. I real­ly don’t want to start over, but I won­der: should I just give up and switch to Word­press?

One Comment

  1. Adrian November 17, 2010

    You know, I think Word­Press is total­ly overkill and it’s sort of annoy­ing to cus­tomize. That said, it’s got a good devel­op­ment com­mu­ni­ty and it has a lot of nice fea­tures.

Leave a comment

Leave a Comment

November 16, 2010 November 16, 2010 meta by Scott [permanent link]