Mercurial > p > roundup > code
comparison doc/installation.txt @ 2921:ad4fb8a14a97
more doc updates, not so many TODOs any more
| author | Richard Jones <richard@users.sourceforge.net> |
|---|---|
| date | Thu, 18 Nov 2004 05:05:25 +0000 |
| parents | 2317e43609cb |
| children | 98efa80f0f90 |
comparison
equal
deleted
inserted
replaced
| 2920:98e6219ddb83 | 2921:ad4fb8a14a97 |
|---|---|
| 296 many simultaneous users, but require much less installation and | 296 many simultaneous users, but require much less installation and |
| 297 maintenance effort than more scalable postgresql and mysql backends. | 297 maintenance effort than more scalable postgresql and mysql backends. |
| 298 If you are choosing from these two, please select sqlite. | 298 If you are choosing from these two, please select sqlite. |
| 299 **postgresql** | 299 **postgresql** |
| 300 Backend for popular RDBMS PostgreSQL. You must read doc/postgresql.txt for | 300 Backend for popular RDBMS PostgreSQL. You must read doc/postgresql.txt for |
| 301 additional installation steps and requirements. | 301 additional installation steps and requirements. You must also configure |
| 302 the ``rdbms`` section of your tracker's ``config.ini`` | |
| 302 **mysql** | 303 **mysql** |
| 303 Backend for popular RDBMS MySQL. You must read doc/mysql.txt for additional | 304 Backend for popular RDBMS MySQL. You must read doc/mysql.txt for additional |
| 304 installation steps and requirements. | 305 installation steps and requirements. You must also configure the ``rdbms`` |
| 306 section of your tracker's ``config.ini`` | |
| 305 | 307 |
| 306 You may defer your decision by setting your tracker up with the anydbm | 308 You may defer your decision by setting your tracker up with the anydbm |
| 307 backend (which is guaranteed to be available) and switching to one of the | 309 backend (which is guaranteed to be available) and switching to one of the |
| 308 other backends at any time using the instructions in the `administration | 310 other backends at any time using the instructions in the `administration |
| 309 guide`_. | 311 guide`_. |
| 593 | 595 |
| 594 If you're using the mysql or postgresql backend then you'll need to ensure | 596 If you're using the mysql or postgresql backend then you'll need to ensure |
| 595 that the tracker user has appropriate permissions to create/modify the | 597 that the tracker user has appropriate permissions to create/modify the |
| 596 database. If you're using roundup.cgi, the apache user needs permissions | 598 database. If you're using roundup.cgi, the apache user needs permissions |
| 597 to modify the database. Alternatively, explicitly specify a database login | 599 to modify the database. Alternatively, explicitly specify a database login |
| 598 in ``POSTRGRESQL_DATABASE`` or ``MYSQL_DATABASE`` in ``config.py``. | 600 in ``rdbms`` -> ``user`` and ``password`` in ``config.ini``. |
| 599 | 601 |
| 600 An alternative to the above is to create a new user who has the sole | 602 An alternative to the above is to create a new user who has the sole |
| 601 responsibility of running roundup. This user: | 603 responsibility of running roundup. This user: |
| 602 | 604 |
| 603 1. runs the CGI interface daemon | 605 1. runs the CGI interface daemon |