Mercurial > p > roundup > code
comparison doc/installation.txt @ 2595:7b2ea468381a maint-0.7
merge from HEAD
| author | Richard Jones <richard@users.sourceforge.net> |
|---|---|
| date | Tue, 20 Jul 2004 04:47:45 +0000 |
| parents | 4a3a3fdcf437 |
| children | d3a8613fd8c3 |
comparison
equal
deleted
inserted
replaced
| 2593:9e1c4c932323 | 2595:7b2ea468381a |
|---|---|
| 473 support:*:1002:jblaine,samh,geezer,mail,apache | 473 support:*:1002:jblaine,samh,geezer,mail,apache |
| 474 | 474 |
| 475 The tracker "db" directory should be chmod'ed g+sw so that the group can | 475 The tracker "db" directory should be chmod'ed g+sw so that the group can |
| 476 write to the database, and any new files created in the database will be owned | 476 write to the database, and any new files created in the database will be owned |
| 477 by the group. | 477 by the group. |
| 478 | |
| 479 If you're using the mysql or postgresql backend then you'll need to ensure | |
| 480 that the tracker user has appropriate permissions to create/modify the | |
| 481 database. If you're using roundup.cgi, the apache user needs permissions | |
| 482 to modify the database. Alternatively, explicitly specify a database login | |
| 483 in ``POSTRGRESQL_DATABASE`` or ``MYSQL_DATABASE`` in ``config.py``. | |
| 478 | 484 |
| 479 An alternative to the above is to create a new user who has the sole | 485 An alternative to the above is to create a new user who has the sole |
| 480 responsibility of running roundup. This user: | 486 responsibility of running roundup. This user: |
| 481 | 487 |
| 482 1. runs the CGI interface daemon | 488 1. runs the CGI interface daemon |