22Administration Guide
33====================
44
5- :Version: $Revision: 1.19 $
5+ :Version: $Revision: 1.20 $
66
77.. contents::
88
@@ -74,7 +74,7 @@ Configuring roundup-server
7474The basic configuration file layout is as follows (take from the
7575``roundup-server.ini.example`` file in the "doc" directory)::
7676
77- [server ]
77+ [main ]
7878 port = 8080
7979 ;hostname =
8080 ;user =
@@ -83,9 +83,9 @@ The basic configuration file layout is as follows (take from the
8383 ;pidfile =
8484 ;logfile =
8585
86+ [trackers]
8687 ; Add one of these per tracker being served
87- [tracker_url_component]
88- home = /path/to/tracker
88+ name = /path/to/tracker/name
8989
9090Values ";commented out" are optional. The meaning of the various options
9191are as follows:
@@ -109,13 +109,10 @@ are as follows:
109109 written to this file. It must be specified if **pidfile** is specified.
110110 If per-tracker logging is specified, then very little will be written to
111111 this file.
112- **example_tracker** sections
113- These are used to specify which Roundup trackers are to be served up by
114- roundup-server. Each tracker has its own ``[section]`` with a single
115- ``home`` value defined pointing to the tracker's home. The section name is
116- used in the URL to select the appropriate reacker. Make sure the name part
117- doesn't include any url-unsafe characters like spaces. Stick to
118- alphanumeric characters and you'll be ok.
112+ **trackers** section
113+ Each line denotes a mapping from a URL component to a tracker home.
114+ Make sure the name part doesn't include any url-unsafe characters like
115+ spaces. Stick to alphanumeric characters and you'll be ok.
119116
120117
121118Users and Security
0 commit comments