Pyblosxom is a python-based web journal ("blog") creation and maintainance program. It supposedly just creates HTML; how it gets online is up to you. This ebuild was made for a friend. Someone more Python savvy than I should also check it. No dependancies besides python itself are known. Reproducible: Always Steps to Reproduce:
Created attachment 17934 [details] pyblosxom-0.8.ebuild the dev-python/pyblosxom/pyblosxom-0.8.ebuild
Actually, I should rephrase that; you need a web server for pyblosxom's CGI program, unless you are using a web browser or some hapazard means than can run CGI's on its own. It may also be possible to drive pyblosxom directly via its xmlrpc API, but the pyblosxom wiz telling me that is not 100% sure. Any web server that supports CGI's can be used, and no web server is required for installation. This ebuild presently does not attempt to copy the CGI's anywhere.
this is sort of a web-apps thing.
please add: RESTRICT="nomirror"
also, remove "S=${WORKDIR}/${P}" because it's already implied.
Pardon me; I'm in the process of moving (see Bug #45773, unrelated). If there is still interest in this 8-month old ebuild and someone wants to edit it within the next few weeks or so, feel free to be my guest. (Note however, pyblosxom is now up to version 0.9.1.)
i've actually started using this (but on a OpenBSD box) and it isn't bad. but i'm not familiar with the webapps setup to know how to make sure it conforms to the web-apps spec. i assume it would be similar setup to www-apps/trac
Created attachment 58633 [details] A new ebuild for the latest version
Here is a new ebuild for version 1.2 of PyBlosxom. I'm also working on a contrib plugin and getting this one to work with webapp-config.
I have also been working on an ebuild for Pyblosxom. Currently I am using webapp-config and a hook script to create data directories. The data, log, and plugin directories are not in the docroot instead they are at the same level as the htdocs directory. Give a webapp in the blog directory I create a stucture like: htdocs/blog/ webapps/blog/data webapps/blog/logs webapps/blog/plugins
Created attachment 58709 [details] PyBlosxom ebuild A webapp-config enabled version of the PyBlosxom plugin.
Created attachment 58710 [details] webapp-config post installation instructions webapp-config post installation instructions.
Created attachment 58711 [details] Sample Apache config Apache configuration file for the webapp directory.
Created attachment 58712 [details] webapp-config hook script webapp-config hook script that creates the data dirctories.
Comment on attachment 58709 [details] PyBlosxom ebuild Sorry wrong content type, w3m is not playing nice today.
Comment on attachment 58710 [details] webapp-config post installation instructions Sorry wrong content type, w3m is not playing nice today.
Comment on attachment 58711 [details] Sample Apache config Sorry wrong content type, w3m is not playing nice today.
Comment on attachment 58712 [details] webapp-config hook script Sorry wrong content type, w3m is not playing nice today.
Created attachment 64819 [details] Ebuild for Pyblosxom Cleanup for the tree. Fixed location of cgi script (now cgi-bin) Moved adding of directories from hook to ebuild. Removed htaccess file
Created attachment 64820 [details] Modified config hook
Created attachment 64821 [details] Modified install instructions
Created attachment 64822 [details] Patch for setup.py
Created attachment 65789 [details] Ebuild for Pyblosxom Fixed keepdir.
Created attachment 65790 [details] Modified config hook Fixed behaviour on error and disregards clean now.
Created attachment 67774 [details] Ebuild for Pyblosxom Fixed keepdir statements.
The new config hook script here bothers me a little bit. While in retrospect I think that my webapps heirarchy was a bit overkill, I don't like having the plugins directory point to the shared directory. That would mean that if you update the contrib package then every thing is updated automatically.
What would be your preferred location for the plugin directory? I did not want to put it into the webroot hierarchy (e.g. ${MY_HTDOCSDIR}/plugins) since the code does not need to be accessed over the web. As long as the cgi-script has access to it it's ok, but it should reside outside of htdocs. What would be your suggestion? And thanks for providing the ebuild!
pyblosxom is now in our unofficial overlay: http://svn.gnqs.org/projects/gentoo-webapps-overlay/browser/experimental/www-apps/phpcodegenie/ Please note that the overlay is unofficial, not a Gentoo project, and not supported. It is intended to provide easier access to new web applications.
Link correction: http://svn.gnqs.org/projects/gentoo-webapps-overlay/browser/experimental/www-apps/pyblosxom
upstream
1.2.1 is finally in portage. 1.3 will be made available as soon as it is being released.