Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

ajt (2546)

  (email not shown publicly)

UK based. Perl, XML/HTTP, SAP, Debian hacker.

  • PerlMonks: ajt []
  • Local LUG: AdamTrickett []
  • Debian Administration: ajt []
  • LinkedIn: drajt []

Journal of ajt (2546)

Tuesday November 25, 2008
07:33 AM

Blogging Engine

[ #37937 ]

I run my personal blog using blosxom. It works and I'm mostly happy with it. After a long period of stagnation there is some work on the tool, which is good.

I recently tried the new revised version and it didn't like my blog's "flavour" data. I had a look at the code and I didn't like it - well not enough to try and fix it.

I can keep my old Blosxom install which does work perfectly well. I could try something else (e.g. Bryar) - but there are not that many light-weight non database blogs about, or I could write my own.

I'm really tempted to write my own, not as a fork of Blosxom, rather a fresh application that can use the same filesystem data, similar templates and possibly a few extra features. My plan would be to create a OO module with a very simple wrapper app that could be a mod_Perl module or CGI script.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
    • I know Steve but had forgotten Chronicle - I'll have to have another look.

      -- "It's not magic, it's work..."
  • Oddly enough I just rewrote blosxom last week. I got tired of patching because it didn't quite exactly match 100% what I wanted it to do. Considering the blog I use it on is static, with relatively few posts, it was easy enough to cobble up something that works just for me.

    Incidently I (and you, apparently) followed exactly the process MJD described in Blosxom Sucks []: first write plugins, then hack the code, then rewrite it.

    In any case, I kinda like blosxom, except for the need to have so many different temp

    • I really like Blosxom's simple design but with simplicity comes the complexity of hacking it to make it work correctly... On my system I wrote my own "flavours" from scratch and hacked the RSS generator so that it creates RSS feeds with valid dates. Other than that I've not hacked it that much...

      I'm currently playing with ikiwiki which is a functionally excellent wiki compiler and I'm wondering if the "compile" design is a good alternative for a blogging engine. You have entries on the filesystem in blosxom

      -- "It's not magic, it's work..."
      • I love the way blosxom is coded, with long lists of statements separated by 'and' or 'or'. That's hell to debug, but fun to read.

        I am a big fan of the "compile" design. I lets me create (and check twice) posts on one machine, generate the blog, check some more, then rsync it to the live server. Of course it's easier when you don't want to handle comments...

        • I like the compile design of ikiwiki which is what made me think of making my own blog compiler that used blosxom style files but generated static xhtml, which is then published via rsync/ssh. Like you I'm not interested in comments or a web form to create fancy content, I just want a simple to use blogging engine.

          The original code is "compact" and while it's nice that some is looking after it, it's hardly idiomatic Perl and that's probably not a good idea on something like a once popular CGI blogging appli

          -- "It's not magic, it's work..."