Mercurial > p > roundup > code
comparison doc/admin_guide.txt @ 3250:8634ea9b2d1c
doc updates
| author | Richard Jones <richard@users.sourceforge.net> |
|---|---|
| date | Thu, 31 Mar 2005 00:45:25 +0000 |
| parents | 33e3ba342e93 |
| children | 74db49467de8 |
comparison
equal
deleted
inserted
replaced
| 3248:f394349adb10 | 3250:8634ea9b2d1c |
|---|---|
| 1 ==================== | 1 ==================== |
| 2 Administration Guide | 2 Administration Guide |
| 3 ==================== | 3 ==================== |
| 4 | 4 |
| 5 :Version: $Revision: 1.16 $ | 5 :Version: $Revision: 1.17 $ |
| 6 | 6 |
| 7 .. contents:: | 7 .. contents:: |
| 8 | 8 |
| 9 What does Roundup install? | 9 What does Roundup install? |
| 10 ========================== | 10 ========================== |
| 64 | 64 |
| 65 (``roundup-mailgw`` always logs to the tracker's log file) | 65 (``roundup-mailgw`` always logs to the tracker's log file) |
| 66 | 66 |
| 67 In both cases, if no logfile is specified then logging will simply be sent | 67 In both cases, if no logfile is specified then logging will simply be sent |
| 68 to sys.stderr with only logging of ERROR messages. | 68 to sys.stderr with only logging of ERROR messages. |
| 69 | |
| 69 | 70 |
| 70 Configuring roundup-server | 71 Configuring roundup-server |
| 71 ========================== | 72 ========================== |
| 72 | 73 |
| 73 The basic configuration file layout is as follows (take from the | 74 The basic configuration file layout is as follows (take from the |
| 161 | 162 |
| 162 1. `tracker backup`_ | 163 1. `tracker backup`_ |
| 163 2. `software upgrade`_ | 164 2. `software upgrade`_ |
| 164 3. `migrating backends`_ | 165 3. `migrating backends`_ |
| 165 4. `moving a tracker`_ | 166 4. `moving a tracker`_ |
| 167 5. `migrating from other software`_ | |
| 166 | 168 |
| 167 | 169 |
| 168 Tracker Backup | 170 Tracker Backup |
| 169 -------------- | 171 -------------- |
| 170 | 172 |
| 253 5. use the roundup-admin "import" command to import the tracker on the new | 255 5. use the roundup-admin "import" command to import the tracker on the new |
| 254 machine, and | 256 machine, and |
| 255 6. start the tracker web and email frontends on the new machine. | 257 6. start the tracker web and email frontends on the new machine. |
| 256 | 258 |
| 257 | 259 |
| 260 Migrating From Other Software | |
| 261 ----------------------------- | |
| 262 | |
| 263 You have a couple of choices. You can either use a CSV import into Roundup, | |
| 264 or you can write a simple Python script which uses the Roundup API | |
| 265 directly. The latter is almost always simpler -- see the "scripts" | |
| 266 directory in the Roundup source for some example uses of the API. | |
| 267 | |
| 268 "roundup-admin import" will import data into your tracker from a | |
| 269 directory containing files with the following format: | |
| 270 | |
| 271 - one colon-separated-values file per Class with columns for each property, | |
| 272 named <classname>.csv | |
| 273 - one colon-separated-values file per Class with journal information, | |
| 274 named <classname>-journals.csv (this is required, even if it's empty) | |
| 275 - if the Class is a FileClass, you may have the "content" property | |
| 276 stored in separate files from the csv files. This goes in a directory | |
| 277 structure:: | |
| 278 | |
| 279 <classname>-files/<N>/<designator> | |
| 280 | |
| 281 where ``<designator>`` is the item's ``<classname><id>`` combination. | |
| 282 The ``<N>`` value is ``int(<id> / 1000)``. | |
| 283 | |
| 284 | |
| 258 Running the Servers | 285 Running the Servers |
| 259 =================== | 286 =================== |
| 260 | 287 |
| 261 Unix | 288 Unix |
| 262 ---- | 289 ---- |