| 15 | | === Some Useful Tips |
| 16 | | - The user under which the web server runs will require file system write permission to |
| 17 | | the environment directory and all the files inside. Please remember to set |
| 18 | | the appropriate permissions. The same applies to the source code repository, |
| 19 | | |
| | 17 | === Useful Tips |
| | 18 | |
| | 19 | - Place your environment's directory on a filesystem which supports sub-second timestamps, as Trac monitors the timestamp of its configuration files and changes happening on a filesystem with too coarse-grained timestamp resolution may go undetected in Trac < 1.0.2. This is also true for the location of authentication files when using TracStandalone. |
| | 20 | |
| | 21 | - The user under which the web server runs will require file system write permission to the environment directory and all the files inside. Please remember to set the appropriate permissions. The same applies to the source code repository, although the user under which Trac runs will only require write access to a Subversion repository created with the BDB file system; for other repository types, check the corresponding plugin's documentation. |
| 31 | | Since version 0.9, Trac supports both [http://sqlite.org/ SQLite] and |
| 32 | | [http://www.postgresql.org/ PostgreSQL] database backends. Preliminary |
| 33 | | support for [http://mysql.com/ MySQL] was added in 0.10. The default is |
| 34 | | to use SQLite, which is probably sufficient for most projects. The database |
| 35 | | file is then stored in the environment directory, and can easily be |
| 36 | | [wiki:TracBackup backed up] together with the rest of the environment. |
| | 33 | Trac supports [http://sqlite.org/ SQLite], [http://www.postgresql.org/ PostgreSQL] and [http://mysql.com/ MySQL] database backends. The default is SQLite, which is probably sufficient for most projects. The database file is then stored in the environment directory, and can easily be [wiki:TracBackup backed up] together with the rest of the environment. |
| 45 | | === PostgreSQL Connection String === |
| 46 | | If you want to use PostgreSQL or MySQL instead, you'll have to use a |
| 47 | | different connection string. For example, to connect to a PostgreSQL |
| 48 | | database on the same machine called `trac`, that allows access to the |
| 49 | | user `johndoe` with the password `letmein`, use: |
| | 45 | === PostgreSQL Connection String |
| | 46 | |
| | 47 | If you want to use PostgreSQL instead, you'll have to use a different connection string. For example, to connect to a PostgreSQL database on the same machine called `trac` for user `johndoe` with the password `letmein` use: |
| 74 | | Generally, the following is sufficient to create a database user named `tracuser`, and a database named `trac`. |
| 75 | | {{{ |
| 76 | | createuser -U postgres -E -P tracuser |
| 77 | | createdb -U postgres -O tracuser -E UTF8 trac |
| 78 | | }}} |
| 79 | | When running `createuser` you will be prompted for the password for the user 'tracuser'. This new user will not be a superuser, will not be allowed to create other databases and will not be allowed to create other roles. These privileges are not needed to run a trac instance. If no password is desired for the user, simply remove the `-P` and `-E` options from the `createuser` command. Also note that the database should be created as UTF8. LATIN1 encoding causes errors trac's use of unicode in trac. SQL_ASCII also seems to work. |
| 80 | | |
| 81 | | Under some default configurations (debian) one will have run the `createuser` and `createdb` scripts as the `postgres` user. For example: |
| 82 | | {{{ |
| 83 | | sudo su - postgres -c 'createuser -U postgres -S -D -R -E -P tracuser' |
| 84 | | sudo su - postgres -c 'createdb -U postgres -O tracuser -E UTF8 trac' |
| | 70 | Generally, the following is sufficient to create a database user named `tracuser` and a database named `trac`: |
| | 71 | {{{#!sh |
| | 72 | $ createuser -U postgres -E -P tracuser |
| | 73 | $ createdb -U postgres -O tracuser -E UTF8 trac |
| 87 | | Trac uses the `public` schema by default but you can specify a different schema in the connection string: |
| | 76 | When running `createuser` you will be prompted for the password for the user 'tracuser'. This new user will not be a superuser, will not be allowed to create other databases and will not be allowed to create other roles. These privileges are not needed to run a Trac instance. If no password is desired for the user, simply remove the `-P` and `-E` options from the `createuser` command. Also note that the database should be created as UTF8. LATIN1 encoding causes errors, because of Trac's use of unicode. SQL_ASCII also seems to work. |
| | 77 | |
| | 78 | Under some default configurations (Debian) one will have run the `createuser` and `createdb` scripts as the `postgres` user: |
| | 79 | {{{#!sh |
| | 80 | $ sudo su - postgres -c 'createuser -U postgres -S -D -R -E -P tracuser' |
| | 81 | $ sudo su - postgres -c 'createdb -U postgres -O tracuser -E UTF8 trac' |
| | 82 | }}} |
| | 83 | |
| | 84 | Trac uses the `public` schema by default, but you can specify a different schema in the connection string: |
| 94 | | If you want to use MySQL instead, you'll have to use a |
| 95 | | different connection string. For example, to connect to a MySQL |
| 96 | | database on the same machine called `trac`, that allows access to the |
| 97 | | user `johndoe` with the password `letmein`, the mysql connection string is: |
| | 91 | The format of the MySQL connection string is similar to those for PostgreSQL, with the `postgres` scheme being replaced by `mysql`. For example, to connect to a MySQL database on the same machine called `trac` for user `johndoe` with password `letmein`: |
| 113 | | For some version control systems, it is possible to specify not only the path to the repository, |
| 114 | | but also a ''scope'' within the repository. Trac will then only show information |
| 115 | | related to the files and changesets below that scope. The Subversion backend for |
| 116 | | Trac supports this; for other types, check the corresponding plugin's documentation. |
| | 107 | For some version control systems, it is possible to specify not only the path to the repository, but also a ''scope'' within the repository. Trac will then only show information related to the files and changesets below that scope. The Subversion backend for Trac supports this. For other types, check the corresponding plugin's documentation. |
| 142 | | * `trac.db` - The SQLite database (if you're using SQLite). |
| 143 | | * `htdocs` - directory containing web resources, which can be referenced in Genshi templates using `/htdocs/site/...` URLs. ''(since 0.11)'' |
| 144 | | * `log` - default directory for log files, if logging is turned on and a relative path is given. |
| 145 | | * `plugins` - Environment-specific [wiki:TracPlugins plugins] (Python eggs or single file plugins, since [trac:milestone:0.10 0.10]) |
| 146 | | * `templates` - Custom Genshi environment-specific templates. ''(since 0.11)'' |
| 147 | | * `site.html` - method to customize header, footer, and style, described in TracInterfaceCustomization#SiteAppearance |
| | 134 | * `trac.db` - The SQLite database, if you are using SQLite. |
| | 135 | * `htdocs` - Directory containing web resources, which can be referenced in Genshi templates using `/chrome/site/...` URLs. |
| | 136 | * `log` - Default directory for log files, if `file` logging is enabled and a relative path is given. |
| | 137 | * `plugins` - Environment-specific [wiki:TracPlugins plugins]. |
| | 138 | * `templates` - Custom Genshi environment-specific templates. |
| | 139 | * `site.html` - Method to customize header, footer, and style, described in TracInterfaceCustomization#SiteAppearance. |
