roundup-demo(1) [debian man page]
ROUNDUP-SERVER(1) General Commands Manual ROUNDUP-SERVER(1) NAME
roundup-demo - create a roundup "demo" tracker and launch its web interface SYNOPSIS
roundup-demo [backend [nuke]] OPTIONS
nuke Create a fresh demo tracker (deleting the existing one if any). If the additional backend argument is specified, the new demo tracker will use the backend named (one of "anydbm", "sqlite", "metakit", "mysql" or "postgresql"; subject to availability on your system). DESCRIPTION
This command creates a fresh demo tracker for you to experiment with. The email features of Roundup will be turned off (so the nosy feature won't send email). It does this by removing the nosyreaction.py module from the demo tracker's detectors directory. If you wish, you may modify the demo tracker by editing its configuration files and HTML templates. See the customisation manual for infor- mation about how to do that. Once you've fiddled with the demo tracker, you may use it as a template for creating your real, live tracker. Simply run the roundup-admin command to install the tracker from inside the demo tracker home directory, and it will be listed as an available template for installa- tion. No data will be copied over. AUTHOR
This manpage was written by Richard Jones <richard@users.sourceforge.net>. 27 July 2004 ROUNDUP-SERVER(1)
Check Out this Related Man Page
ROUNDUP-MAILGW(1) General Commands Manual ROUNDUP-MAILGW(1) NAME
roundup-mailgw - mail gateway for roundup SYNOPSIS
roundup-mailgw instance_home [method] OPTIONS
-v Print version and exit. -C hyperdb class specify a tracker class - one of msg (the default), issue, file, user - to manipulate with -S options -S property=value[;property=value] pairs specify the values to set on the class specified by -C using the same format as the Subject line property manipulations DESCRIPTION
The roundup mail gateway may be called in one of three ways: o with an instance home as the only argument, o with both an instance home and a mail spool file, or o with both an instance home and a pop server account. PIPE In the first case, the mail gateway reads a single message from the standard input and submits the message to the roundup.mailgw module. UNIX mailbox In the second case, the gateway reads all messages from the mail spool file and submits each in turn to the roundup.mailgw module. The file is emptied once all messages have been successfully handled. The file is specified as: mailbox /path/to/mailbox In all of the following the username and password can be stored in a ~/.netrc file. In this case only the server name need be specified on the command-line. The username and/or password will be prompted for if not supplied on the command-line or in ~/.netrc. POP In the third case, the gateway reads all messages from the POP server specified and submits each in turn to the roundup.mailgw module. The server is specified as: pop username:password@server The username and password may be omitted: pop username@server pop server are both valid. The username and/or password will be prompted for if not supplied on the command-line. APOP Same as POP, but using Authenticated POP: apop username:password@server IMAP Connect to an IMAP server. This supports the same notation as that of POP mail. imap username:password@server It also allows you to specify a specific mailbox other than INBOX using this format: imap username:password@server mailbox IMAPS Connect to an IMAP server over ssl. This supports the same notation as IMAP. imaps username:password@server [mailbox] AUTHOR
This manpage was written by Bastian Kleineidam <calvin@debian.org> for the Debian distribution of roundup. The main author of roundup is Richard Jones <richard@users.sourceforge.net>. 24 January 2003 ROUNDUP-MAILGW(1)