Mercurial > p > roundup > code
view share/man/man1/roundup-demo.1 @ 5729:9ea2ce9d10cf
A few internet references report that etags for the same underlying
resource but with different representation (xml, json ...) should have
different etags.
That is currently not the case. Added code to allow incorporation of
representation info into the etag. By default the representation is
"json", but future patches can pass the representation down and modify
flow to match requested representation.
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Sat, 25 May 2019 14:23:16 -0400 |
| parents | ab542607f2fb |
| children | 47a521b9ebb9 |
line wrap: on
line source
.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", "metakit", "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>.
