diff --git a/doc/installation.txt b/doc/installation.txt
index 17442e4bac571ac6e698f49e5505074421b18214..7c0741c060b920d608386e5d5da6cf74283f1f53 100644 (file)
--- a/doc/installation.txt
+++ b/doc/installation.txt
Installing Roundup
==================
-:Version: $Revision: 1.58 $
+:Version: $Revision: 1.67 $
.. contents::
Prerequisites
=============
-Python 2.1.1 or newer with a functioning anydbm or bsddb module. Download the
-latest version from http://www.python.org/. It is highly recommended that
-users install the latest patch version of python - 2.1.3 or 2.2.3 - as these
-contain many fixes to serious bugs. Python 2.3 (currently in beta) has some
-"issues", at least with the SQLite backend, and possibly with other backends
-as well. It shouldn't be used with Roundup for now.
+Roundup requires Python 2.1.3 or newer with a functioning anydbm or
+bsddb module. Download the latest version from http://www.python.org/.
+It is highly recommended that users install the latest patch version
+of python as these contain many fixes to serious bugs.
If you want to use Berkeley DB bsddb3 with Roundup, use version 3.3.0 or
later. Download the latest version from http://pybsddb.sourceforge.net/.
Testing your Python
-------------------
-Once you've unpacked roundup's source, run ``python ./run_tests`` in the
-source directory and make sure there are no errors.
-If there are errors, please let us know!
+Once you've unpacked roundup's source, run ``python run_tests.py`` in the
+source directory and make sure there are no errors. If there are errors,
+please let us know!
If the above fails, you may be using the wrong version of python. Try
-``python2 ./run_tests``. If that works, you will need to substitute
+``python2 run_tests.py``. If that works, you will need to substitute
``python2`` for ``python`` in all further commands you use in relation to
Roundup -- from installation and scripts.
Installation
============
-Note: some systems, such as Debian and NetBSD, already have Roundup
- installed. Try running the command "roundup-admin" with no arguments,
- and if it runs you may skip the `Basic Installation Steps`_
- below.
+:Note: Some systems, such as Debian and NetBSD, already have Roundup
+ installed. Try running the command "roundup-admin" with no arguments,
+ and if it runs you may skip the `Basic Installation Steps`_
+ below and go straight to `configuring your first tracker`_.
Set aside 15-30 minutes. Please make sure you're using a supported version of
Python -- see `testing your python`_. There's several steps to follow in your
2. `configuring your first tracker`_ that all installers must follow
3. then optionally `configure a web interface`_
4. and optionally `configure an email interface`_
-5. `shared environment steps`_ to take if you're installing on a shared
+5. `UNIX environment steps`_ to take if you're installing on a shared
UNIX machine and want to restrict local access to roundup
+6. `additional language codecs`_
+
+For information about how Roundup installs, see the `maintenance
+documentation`_.
Basic Installation Steps
then direct your web browser at:
- http://locahost:8080/support/
+ http://localhost:8080/support/
and you should see the tracker interface.
**mysql**
Backend for popular RDBMS MySQL. According to benchmarks, this backend works
much faster than any of \*dbm ones, but slightly slower than metakit and
- sqlite. A good scalability is not a property of this backend for now,
- though. For more info on backend installation see doc/mysql.txt.
+ sqlite. You must read doc/mysql.txt for additional installation steps and
+ requirements.
+**postgresql**
+ Backend for popular RDBMS PostgreSQL. According to benchmarks, this
+ backend works much faster than any of \*dbm ones and mysql, but slightly
+ slower than metakit and sqlite. You must read doc/postgresql.txt for
+ additional installation steps and requirements.
**metakit**
This backend is implemented over the metakit_ storage system, using Mk4Py as
the interface. It scales much better than the dbm backends.
3. `Zope product - ZRoundup`_
You may need to give the web server user permission to access the tracker home
-- see the `shared environment steps`_ for information. You may also need to
+- see the `UNIX environment steps`_ for information. You may also need to
configure your system in some way - see `platform-specific notes`_.
To make the server run in the background, use the "-d" option, specifying the
name of a file to write the server process id (pid) to.
-To run the server proxied through apache (to take advantage of SSL or other
-apache features), use the following configuration lines::
-
- LoadModule proxy_module libexec/apache2/mod_proxy.so
- LoadModule proxy_connect_module libexec/apache2/mod_proxy_connect.so
- LoadModule proxy_http_module libexec/apache2/mod_proxy_http.so
-
- <Location /prometheus/>
- ProxyPass http://192.168.1.2:9090/roundup/
- AuthType Basic
- AuthName Roundup
- AuthUserFile /some/place/htpasswd
- Require valid-user
- </Location>
-
-Changing the ProxyPass line to point to the server you're running.
-
Zope Product - ZRoundup
~~~~~~~~~~~~~~~~~~~~~~~
Set ``roundup-mailgw`` up to run every 10 minutes or so. For example::
- 10 * * * * /usr/local/bin/roundup-mailgw /opt/roundup/trackers/support mailbox <mail_spool_file>
+ 0,10,20,30,40,50 * * * * /usr/local/bin/roundup-mailgw /opt/roundup/trackers/support mailbox <mail_spool_file>
Where the ``mail_spool_file`` argument is the location of the roundup submission
user's mail spool. On most systems, the spool for a user "issue_tracker"
As a regular job using a POP source
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-To retrieve from a POP mailbox, use a *cron* entry to the mailbox one::
+To retrieve from a POP mailbox, use a *cron* entry similar to the mailbox one::
- 10 * * * * /usr/local/bin/roundup-mailgw /opt/roundup/trackers/support pop <pop_spec>
+ 0,10,20,30,40,50 * * * * /usr/local/bin/roundup-mailgw /opt/roundup/trackers/support pop <pop_spec>
where pop_spec is "``username:password@server``" that specifies the roundup
submission user's POP account name, password and server.
On windows, you would set up the command using the windows scheduler.
-Shared Environment Steps
-------------------------
+UNIX Environment Steps
+----------------------
Each tracker ideally should have its own UNIX group, so create
a UNIX group (edit ``/etc/group`` or your appropriate NIS map if
may actually login and play with the roundup setup.
+Additional Language Codecs
+--------------------------
+
+If you intend to send messages to Roundup that use Chinese, Japanese or
+Korean encodings the you'll need to obtain CJKCodecs from
+http://cjkpython.berlios.de/
+
+
Maintenance
===========
Linux
-----
-Make sure you read the instructions under `shared environment steps`_.
+Make sure you read the instructions under `UNIX environment steps`_.
Python 2.1.1 as shipped with SuSE7.3 might be missing module
``_weakref``.
You'll need to build Python.
-Make sure you read the instructions under `shared environment steps`_.
+Make sure you read the instructions under `UNIX environment steps`_.
+
-------------------------------------------------------------------------------