PyBlosxom is a lightweight weblog system. It was originally a Python clone of Blosxom but has since evolved into a weblog system of its own reminiscent of Blosxom.
PyBlosxom focuses on three things:
simplicity
PyBlosxom stores all data on the file system in plain text files. This allows you to use any text editor to create, update and manipulate entries. You can also use existing text-manipulation tools, version control, scripts, grep, ... for managing your blog.
PyBlosxom can run as a CGI script, WSGI component or you can use it to statically compile your website into HTML/XML files.
Your workflow is your workflow.
extensibility
PyBlosxom has a plugin framework enabling you to augment and enhance PyBlosxom’s default behavior. Plugins are written in Python. We maintain a list of plugins in the plugin registry on the website.
Plugins aren’t hard to write. We’re happy to help you write plugins.
community
There are several hundred PyBlosxom users out there all of whom have different needs. PyBlosxom is used on a variety of operating systems in a variety of environments. We have the standard open source project fare: mailing lists, IRC channel, wiki, ...
PyBlosxom is built to let you use existing text-manipulation tools without having to build the whole ecology from scratch.
PyBlosxom can be run as:
PyBlosxom is a small open source project and while there is a community, it’s pretty small. PyBlosxom’s features are great but make it a niche weblog engine.
PyBlosxom is a file-based weblog system. Each blog entry is a separate file stored in a directory hierarchy on your file system. By default, the hierarchy is a category tree meaning each blog entry belongs in a single category. By default, mtimes are used as the blog entry timestamp. There are plugins that change this behavior, but require extra configuration to use.
There are a lot of other weblog systems out there. If it’s apparent that PyBlosxom won’t work for you, don’t force it—use something else.
Entries, categories, storage:
Themes:
Plugins:
See http://pyblosxom.bluesock.org/contact for details on the mailing lists, IRC, source code, issue tracker, and everything else.
Read the INSTALL document as well as other documents in the docs/ directory.
If you’re upgrading from a previous PyBlosxom version, read the UPGRADE document as well as CHANGELOG which covers what’s new in this version and what you’ll need to change in your blog.
There’s a series of text files in the docs/ directory which comprise the current state of the PyBlosxom manual at the time of this release.
The most current version of the manual can be found on the PyBlosxom website .
We really appreciate people helping out.
If you discover a problem with PyBlosxom, please let us know on IRC (#pyblosxom on irc.freenode.net) or on the mailing lists.
If you can additionally fix it, attach a patch file to the bug or send the patch as an attachment to the pyblosxom-devel mailing list. When sending a patch, please make sure to describe the details of the problem you are fixing.
Tests are written with the Python unittest module.
To run core tests, do this:
python setup.py test
This will build PyBlosxom, then run the tests.
To run plugin unit tests do this:
PYTHONPATH=. python plugins/testrunner.py
That will run all the plugins tests.
If you would like to add tests to the test suite, please do and send us patches!