I’ve just mailed Sarabian a bit of advice on how I set up Pyblosxom websites. Note that this is probably pretty specific to me, but I present the advice below anyway in case it’s useful to someone else:
I tend to set it up like this:
/var/www/example.org
/html
/pyblosxom
/pyblosxom.cgi
/config.py
/.htaccess [1]
/pyblosxom
/Pyblosxom [2]
/plugins [3]
/sites
/blogging-hacks
[1] content is:
<Files config.py>
deny from all
</Files>
[2] This is the Pyblosxom distribution
[3] Put all your plugins in here
Then set, in config.py, py[‘datadir‘]=‘/var/www/example.org/sites‘,
py[‘plugins_dir‘]=‘/var/www/example.org/plugins‘, and set the base
(the thing which tells it where Pyblosxom itself is, I can’t remember)
to /var/www/example.org/pyblosxom. Then set up an Apache rewrite rule,
something like
RewriteRule /weblogs(.*) /pyblosxom/pyblosxom.cgi$1and then it should all work.
I’ve just started using pyblosxom after using blosxom for perhaps a year.
It’s working well so far, apart from a bug with the calendar.
Dare I ask what you’re plugins are?
Posted by David Goodwin on February 1st, 2005.
David: most of my plugins are custom written things to make kryogenix.org work like I want it to, rather than things that are useful to other people. I use quite a few plugins taken from the plugin repository, though.
Posted by sil on February 1st, 2005.