Version: | $Revision$ |
---|
There's two "installations" that we talk about when using Roundup:
The installation of the software and its support files. This uses the standard Python mechanism called "distutils" and thus Roundup's core code, executable scripts and support data files are installed in Python's directories. On Windows, this is typically:
<python dir>\scripts\...
<python dir>\lib\site-packages\roundup\...
<python dir>\share\roundup\...
and on Unix-like systems (eg. Linux):
<python root>/bin/...
<python root>/lib-<python version>/site-packages/roundup/...
<python root>/share/roundup/...
The installation of a specific tracker. When invoking the roundup-admin "inst" (and "init") commands, you're creating a new Roundup tracker. This installs configuration files, HTML templates, detector code and a new database. You have complete control over where this stuff goes through both choosing your "tracker home" and the DATABASE variable in config.py.
Roundup holds its own user database which primarily contains a username, password and email address for the user. Roundup must have its own user listing, in order to maintain internal consistency of its data. It is a relatively simple exercise to update this listing on a regular basis, or on demand, so that it matches an external listing (eg. unix passwd file, LDAP, etc.)
Roundup identifies users in a number of ways:
In both cases, Roundup's behaviour when dealing with unknown users is controlled by Permissions defined in the "SECURITY SETTINGS" section of the tracker's dbinit.py module:
More information about how to customise your tracker's security settings may be found in the customisation documentation.
Maintenance of Roundup can involve one of the following:
Stop the web and email frontends and to copy the contents of the tracker home directory to some other place using standard backup tools.
Always make a backup of your tracker before upgrading software. Steps you may take:
If you're moving the tracker to a similar machine, you should:
Most of the backends are actually portable across platforms (ie. from Unix to Windows to Mac). If this isn't the case (ie. the tracker doesn't work when moved using the above steps) then you'll need to:
On Unix systems, use the scripts/server-ctl script to control the roundup-server server. Copy it somewhere and edit the variables at the top to reflect your specific installation.
On Windows, the roundup-server program runs as a Windows Service, and therefore may be controlled through the Services control panel.
TODO: info how to bring up the services panel.
TODO: how to start the server in "service" mode.
On windows, use:
roundup-server -c stop
to stop the running server.
The mail gateway script should be scheduled to run regularly on your Windows server. Normally this will result in a window popping up. The solution to this is to:
Back to Table of Contents