I've been debating on whether to start blogging with one Blog or with three: one for centered around my professional work of Cisco networks, one about open source tools I've encountered, and one for detailing the trials and tribulations of developing an automated trading solution. Well, it is one for now.
My first entry has to do with Blosxom. I've been a perl programmer for a while and
wanted
to stay with Perl. Blosxom, at first blush
seems to fit the bill. Now let's see if I can
integrate it in with Mason, upon which my web site is based. I've just been told by the
Blosxom installation instructions I should write something. So here goes. Let's see if
I can get it broadcast to the world!
.... One second while I fire up my web browser to Ray's of Sunshine.
Wow, as advertised, 15 minutes or less. Success. And that was with reading the
instructions!
Well, I
can see the blog entry, but integrated with Mason and the rest of my web site, it isn't.
I'll skip that for the time being. Having read further into the instructions, it looks like
I won't need to create a different site for each train of thought. All I need to do is
create some subdirectories. Blosxom then mixes and matches, automagically.
The Blosxom/Mason connection continued to pry at my skull. ... Some googling later, or
is that some Googling later... so I landed on Life of a Sysadmin
where the fellow talks about support for Blosxom. That provided a good introduction where I
can find support. Also, during that same search, I encountered a Blosxom blog by the Perl
Master himself, David Wheeler at Just a
Theory where he discusses mod_rewrite rules to incorporate Blosxom into Mason. Now that I have the links, I can come
back at my liesure and do some hacking/integrating.
For my further reference, here is The Unofficial Blosxom User Group.