comparison doc/admin_guide.txt @ 3467:8fcee705ebdb maint-0.8

merge from HEAD
author Richard Jones <richard@users.sourceforge.net>
date Fri, 13 Jan 2006 03:34:34 +0000
parents ee1e2c8472f3
children
comparison
equal deleted inserted replaced
3462:639a3d1014e9 3467:8fcee705ebdb
1 ==================== 1 ====================
2 Administration Guide 2 Administration Guide
3 ==================== 3 ====================
4 4
5 :Version: $Revision: 1.15.2.3 $ 5 :Version: $Revision: 1.15.2.4 $
6 6
7 .. contents:: 7 .. contents::
8 8
9 What does Roundup install? 9 What does Roundup install?
10 ========================== 10 ==========================
71 ========================== 71 ==========================
72 72
73 The basic configuration file layout is as follows (take from the 73 The basic configuration file layout is as follows (take from the
74 ``roundup-server.ini.example`` file in the "doc" directory):: 74 ``roundup-server.ini.example`` file in the "doc" directory)::
75 75
76 [server] 76 [main]
77 port = 8080 77 port = 8080
78 ;hostname = 78 ;hostname =
79 ;user = 79 ;user =
80 ;group = 80 ;group =
81 ;log_ip = yes 81 ;log_ip = yes
82 ;pidfile = 82 ;pidfile =
83 ;logfile = 83 ;logfile =
84 84
85 [trackers]
85 ; Add one of these per tracker being served 86 ; Add one of these per tracker being served
86 [tracker_url_component] 87 name = /path/to/tracker/name
87 home = /path/to/tracker
88 88
89 Values ";commented out" are optional. The meaning of the various options 89 Values ";commented out" are optional. The meaning of the various options
90 are as follows: 90 are as follows:
91 91
92 **port** 92 **port**
106 **logfile** 106 **logfile**
107 Any unhandled exception messages or other output from Roundup will be 107 Any unhandled exception messages or other output from Roundup will be
108 written to this file. It must be specified if **pidfile** is specified. 108 written to this file. It must be specified if **pidfile** is specified.
109 If per-tracker logging is specified, then very little will be written to 109 If per-tracker logging is specified, then very little will be written to
110 this file. 110 this file.
111 **example_tracker** sections 111 **trackers** section
112 These are used to specify which Roundup trackers are to be served up by 112 Each line denotes a mapping from a URL component to a tracker home.
113 roundup-server. Each tracker has its own ``[section]`` with a single 113 Make sure the name part doesn't include any url-unsafe characters like
114 ``home`` value defined pointing to the tracker's home. The section name is 114 spaces. Stick to alphanumeric characters and you'll be ok.
115 used in the URL to select the appropriate reacker. Make sure the name part
116 doesn't include any url-unsafe characters like spaces. Stick to
117 alphanumeric characters and you'll be ok.
118 115
119 116
120 Users and Security 117 Users and Security
121 ================== 118 ==================
122 119

Roundup Issue Tracker: http://roundup-tracker.org/