Warning: these instructions still need a lot of help, and I'm not sure that I like this particular installation design in any case. This stuff is here for now, but I'm going to work on an installer/configurator to ease all of this.
There are two major steps for installing and configuring SubWiki.
SubWiki requires a Subversion server installation and the Python/SWIG bindings. This is a rather heavy burden, especially until that day when Subversion is easily and typically installed on most systems. To get all of these Subversion pieces pulled together and built, you will need:
See the Subversion installation instructions for building and installing a Subversion server.
Installing subversion 0.29 from RPMs was pretty straightforward. I had to uninstall a some Apache modules and a couple other things because of dependencies to an old version. Since subWiki doesn't require you to set up access to the repository through Apache, you could leave this out, but the install order below should still work. If you didn't install Apache with the distribution some of the rpm commands in this script might fail, and you might need to change the -U to -i:
rpm --erase mod_perl-1.99_07-5 mod_python-3.0.1-3 php-4.2.2-17 \
mod_auth_mysql-1.11-12 mod_auth_pgsql-0.9.12-14 \
php-imap-4.2.2-17 php-ldap-4.2.2-17
rpm -i apr-0.9.4-0.1.i386.rpm apr-util-0.9.4-0.1.i386.rpm
rpm -U httpd-2.0.47-0.1.i386.rpm httpd-manual-2.0.47-0.1.i386.rpm \
mod_ssl-2.0.47-0.1.i386.rpm swig-1.3.16-1.i386.rpm
rpm -i neon-0.23.9-1.i386.rpm subversion-0.29.0-6982.rh90.i386.rpm \
subversion-server-0.29.0-6982.rh90.i386.rpm \
swig-runtime-1.3.16-1.i386.rpm
rpm -i --nodeps subversion-tools-0.29.0-6982.rh90.i386.rpm
rpm -i subversion-python-0.29.0-6982.rh90.i386.rpm
This probably still needs a lot of work, but after installing
on RedHat 9 with the old notes, I (gerry at geraldgleason.com)
added some more detail to smooth over the rouqh spots.
future: I'd like installation and test-install scripts
So would I (gerry).
SubWiki is designed to run on top of a Subversion repository. The first step to a SubWiki site is creating a Subversion repository. See the Subversion documentation for instructions on how to create the repository and configure Apache.
Fetch the SubWiki package using subversion, something like this:
svn checkout http://svn.webdav.org/repos/projects/subwiki/trunk subwikishould work.
Install files, python library, templates and scripts acording to this map:
| From | To | File Count |
| <install source>/lib | <repos>/third-party/lib | 12 |
| <install source>/plugins | <repos>/third-party/plugins | 7 |
| <install source>/templates/runtime/*.ezt | <repos>/third-party/subwiki/templates/ | 6 |
| <install source>/scripts/subwiki.cgi | <repos>/third-party/subwiki/subwiki.cgi | 1 |
| <install source>/scripts/run-indexer.py | /usr/lib/subversion/tools/hook-scripts/run-indexer.py | 1 |
| Edit <install source>/conf/subwiki.conf.dist | Install in <repos>/third-party/conf/subwiki.conf | 1 |
Create directories as necessary, and chown everything to the Apache user. The cgi script finds the config file from the command path, and the library path is configured in that file. If this mechanism fails, the path can be set in the subwiki.cgi script.