Mercurial > p > roundup > code
comparison doc/installation.txt @ 1317:28ae91aae74f
clarifications
| author | Richard Jones <richard@users.sourceforge.net> |
|---|---|
| date | Mon, 09 Dec 2002 02:37:20 +0000 |
| parents | dd43853684d4 |
| children | 3481507d6098 |
comparison
equal
deleted
inserted
replaced
| 1316:dd43853684d4 | 1317:28ae91aae74f |
|---|---|
| 1 ================== | 1 ================== |
| 2 Installing Roundup | 2 Installing Roundup |
| 3 ================== | 3 ================== |
| 4 | 4 |
| 5 :Version: $Revision: 1.36 $ | 5 :Version: $Revision: 1.37 $ |
| 6 | 6 |
| 7 .. contents:: | 7 .. contents:: |
| 8 | 8 |
| 9 | 9 |
| 10 Overview | 10 Overview |
| 82 | 82 |
| 83 Basic Installation Steps | 83 Basic Installation Steps |
| 84 ------------------------ | 84 ------------------------ |
| 85 | 85 |
| 86 1. To install the Roundup support code into your Python tree and | 86 1. To install the Roundup support code into your Python tree and |
| 87 Roundup scripts into /usr/local/bin. You need to have write permissions | 87 Roundup scripts into /usr/local/bin (substitute that path for whatever is |
| 88 appropriate on your system). You need to have write permissions | |
| 88 for these locations, eg. being root on unix:: | 89 for these locations, eg. being root on unix:: |
| 89 | 90 |
| 90 python setup.py install | 91 python setup.py install |
| 91 | 92 |
| 92 If you would like to place the Roundup scripts in a directory other | 93 If you would like to place the Roundup scripts in a directory other |
| 317 | 318 |
| 318 To test the mail gateway on unix systems, try:: | 319 To test the mail gateway on unix systems, try:: |
| 319 | 320 |
| 320 echo test |mail -s '[issue] test' support@YOUR_DOMAIN_HERE | 321 echo test |mail -s '[issue] test' support@YOUR_DOMAIN_HERE |
| 321 | 322 |
| 322 As a regular cron job using a mailbox source | 323 As a regular job using a mailbox source |
| 323 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | 324 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 324 | 325 |
| 325 Set ``roundup-mailgw`` up to run every 10 minutes or so. For example:: | 326 Set ``roundup-mailgw`` up to run every 10 minutes or so. For example:: |
| 326 | 327 |
| 327 10 * * * * /usr/local/bin/roundup-mailgw /opt/roundup/trackers/support mailbox <mail_spool_file> | 328 10 * * * * /usr/local/bin/roundup-mailgw /opt/roundup/trackers/support mailbox <mail_spool_file> |
| 328 | 329 |
| 329 Where the ``mail_spool_file`` argument is the location of the roundup submission | 330 Where the ``mail_spool_file`` argument is the location of the roundup submission |
| 330 user's mail spool. On most systems, the spool for a user "issue_tracker" | 331 user's mail spool. On most systems, the spool for a user "issue_tracker" |
| 331 will be "``/var/mail/issue_tracker``". | 332 will be "``/var/mail/issue_tracker``". |
| 332 | 333 |
| 333 As a regular cron job using a POP source | 334 As a regular job using a POP source |
| 334 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | 335 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 335 | 336 |
| 336 To retrieve from a POP mailbox, use a similar cron entry to the mailbox one:: | 337 To retrieve from a POP mailbox, use a *cron* entry to the mailbox one:: |
| 337 | 338 |
| 338 10 * * * * /usr/local/bin/roundup-mailgw /opt/roundup/trackers/support pop <pop_spec> | 339 10 * * * * /usr/local/bin/roundup-mailgw /opt/roundup/trackers/support pop <pop_spec> |
| 339 | 340 |
| 340 where pop_spec is "``username:password@server``" that specifies the roundup | 341 where pop_spec is "``username:password@server``" that specifies the roundup |
| 341 submission user's POP account name, password and server. | 342 submission user's POP account name, password and server. |
| 343 | |
| 344 On windows, you would set up the command using the windows scheduler. | |
| 342 | 345 |
| 343 | 346 |
| 344 Shared Environment Steps | 347 Shared Environment Steps |
| 345 ------------------------ | 348 ------------------------ |
| 346 | 349 |