Changes between Version 2 and Version 3 of TracEnvironment
- Timestamp:
- Mar 29, 2016, 11:16:23 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracEnvironment
v2 v3 14 14 15 15 === Some Useful Tips 16 17 - 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). 18 16 19 - The user under which the web server runs will require file system write permission to 17 20 the environment directory and all the files inside. Please remember to set … … 36 39 [wiki:TracBackup backed up] together with the rest of the environment. 37 40 41 Note that if the username or password of the connection string (if applicable) contains the `:`, `/` or `@` characters, they need to be URL encoded. 42 38 43 === SQLite Connection String === 39 44 The connection string for an SQLite database is: … … 51 56 postgres://johndoe:letmein@localhost/trac 52 57 }}} 53 ''Note that due to the way the above string is parsed, the "/" and "@" characters cannot be part of the password.''54 58 55 59 If PostgreSQL is running on a non-standard port (for example 9342), use: … … 92 96 === MySQL Connection String === 93 97 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 98 The format of the MySQL connection string is similar to the examples presented for PostgreSQL, with the `postgres` schema being replaced by `mysql`. For example, to connect to a MySQL 99 database on the same machine called `trac`, allowing access to the 97 100 user `johndoe` with the password `letmein`, the mysql connection string is: 98 101 {{{
