Refactor session db logging and key generation for sessions/otks While I was working on the redis sessiondb stuff, I noticed that log_wanrning, get_logger ... was duplicated. Also there was code to generate a unique key for otks that was duplicated. Changes: creating new sessions_common.py and SessionsCommon class to provide methods: log_warning, log_info, log_debug, get_logger, getUniqueKey getUniqueKey method is closer to the method used to make session keys in client.py. sessions_common.py now report when random_.py chooses a weak random number generator. Removed same from rest.py. get_logger reconciles all logging under roundup.hyperdb.backends.<name of BasicDatabase class> some backends used to log to root logger. have BasicDatabase in other sessions_*.py modules inherit from SessionCommon. change logging to use log_* methods. In addition: remove unused imports reported by flake8 and other formatting changes modify actions.py, rest.py, templating.py to use getUniqueKey method. add tests for new methods test_redis_session.py swap out ModuleNotFoundError for ImportError to prevent crash in python2 when redis is not present. allow injection of username:password or just password into redis connection URL. set pytest_redis_pw envirnment variable to password or user:password when running test.

.TH ROUNDUP-SERVER 1 "27 July 2004"
.SH NAME
roundup-demo \- create a roundup "demo" tracker and launch its web interface
.SH SYNOPSIS
\fBroundup-demo\fP [\fIbackend\fP [\fBnuke\fP]]
.SH OPTIONS
.TP
\fBnuke\fP
Create a fresh demo tracker (deleting the existing one if any). If the
additional \fIbackend\fP argument is specified, the new demo tracker will
use the backend named (one of "anydbm", "sqlite", "mysql" or
"postgresql"; subject to availability on your system).
.SH 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 \fInosyreaction.py\fP module
from the demo tracker's \fIdetectors\fP directory.

If you wish, you may modify the demo tracker by editing its configuration
files and HTML templates. See the \fIcustomisation\fP manual for
information 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 \fIroundup-admin\fP
command to install the tracker from inside the demo tracker home directory,
and it will be listed as an available template for installation. No data
will be copied over.
.SH AUTHOR
This manpage was written by Richard Jones
<richard@users.sourceforge.net>.