Changes between Version 1 and Version 2 of TracEnvironment
- Timestamp:
- 2008-02-26T19:44:04Z (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracEnvironment
v1 v2 5 5 == Creating an Environment == 6 6 7 A new Trac environment is created using [wiki:TracAdmin trac-admin]:7 A new Trac environment is created using [wiki:TracAdmin trac-admin]: 8 8 {{{ 9 $ trac-admin /path/to/ projectenvinitenv9 $ trac-admin /path/to/myproject initenv 10 10 }}} 11 11 … … 22 22 == Database Connection Strings == 23 23 24 Since version 0.9, Trac supports both [http://sqlite.org/ SQLite] ,25 [http://www.postgresql.org/ PostgreSQL] and [http://mysql.com/ MySQL] as26 database backends. The default is to use SQLite, which is probably sufficient 27 for most projects. The database file is then stored in the environment 28 directory, and can easily be [wiki:TracBackup backed up] together with the 29 rest of the environment.24 Since version 0.9, Trac supports both [http://sqlite.org/ SQLite] and 25 [http://www.postgresql.org/ PostgreSQL] database backends. Preliminary 26 support for [http://mysql.com/ MySQL] was added in 0.10. The default is 27 to use SQLite, which is probably sufficient for most projects. The database 28 file is then stored in the environment directory, and can easily be 29 [wiki:TracBackup backed up] together with the rest of the environment. 30 30 31 === Embedded SQLite Connection String === 31 32 The connection string for an embedded SQLite database is: 32 33 {{{ … … 34 35 }}} 35 36 37 === PostgreSQL Connection String === 36 38 If you want to use PostgreSQL or MySQL instead, you'll have to use a 37 39 different connection string. For example, to connect to a PostgreSQL … … 41 43 postgres://johndoe:letmein@localhost/trac 42 44 }}} 45 ''Note that due to the way the above string is parsed, the "/" and "@" characters cannot be part of the password.'' 43 46 44 47 If PostgreSQL is running on a non-standard port (for example 9342), use: … … 47 50 }}} 48 51 52 On UNIX, you might want to select a UNIX socket for the transport, 53 either the default socket as defined by the PGHOST environment variable: 54 {{{ 55 postgres://user:password@/database 56 }}} 57 or a specific one: 58 {{{ 59 postgres://user:password@/database?host=/path/to/socket/dir 60 }}} 61 49 62 Note that with PostgreSQL you will have to create the database before running 50 63 `trac-admin initenv`. 51 64 52 And make sure PostgreSQl DB name is "trac". What worked for me: 53 And didn't work uppercase trac-user-name 65 See the [http://www.postgresql.org/docs/ PostgreSQL documentation] for detailed instructions on how to administer [http://postgresql.org PostgreSQL]. 66 Generally, the following is sufficient to create a database user named `tracuser`, and a database named `trac`. 54 67 {{{ 55 sudo su - postgres -c createdb trac 56 sudo su - postgres -c psql trac 57 CREATE USER trac-user-name WITH PASSWORD 'trac-pass-name'; 68 createuser -U postgres -E -P tracuser 69 createdb -U postgres -O tracuser -E UTF8 trac 70 }}} 71 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. 72 73 Under some default configurations (debian) one will have run the `createuser` and `createdb` scripts as the `postgres` user. For example: 74 {{{ 75 sudo su - postgres -c 'createuser -U postgres -S -D -R -E -P tracuser' 76 sudo su - postgres -c 'createdb -U postgres -O tracuser -E UTF8 trac' 58 77 }}} 59 78 60 (Just to remind you, if you don't have a sudo/su setup, you just need to do the createdb and psql statements. That threw me the first couple of times I read this.) 79 Trac uses the `public` schema by default but you can specify a different schema in the connection string: 80 {{{ 81 postgres://user:pass@server/database?schema=yourschemaname 82 }}} 83 84 === MySQL Connection String === 85 86 If you want to use MySQL instead, you'll have to use a 87 different connection string. For example, to connect to a MySQL 88 database on the same machine called `trac`, that allows access to the 89 user `johndoe` with the password `letmein`, the mysql connection string is: 90 {{{ 91 mysql://johndoe:letmein@localhost:3306/trac 92 }}} 61 93 62 94 == Source Code Repository == … … 98 130 * `db` 99 131 * `trac.db` - The SQLite database (if you're using SQLite). 100 * `plugins` - Environment-specific [wiki:TracPlugins plugins] (Python eggs )132 * `plugins` - Environment-specific [wiki:TracPlugins plugins] (Python eggs, since [milestone:0.10]) 101 133 * `templates` - Custom environment-specific templates. 102 134 * `site_css.cs` - Custom CSS rules. 103 135 * `site_footer.cs` - Custom page footer. 104 136 * `site_header.cs` - Custom page header. 105 * `wiki-macros` - Environment-specific [wiki: WikiMacros Wiki macros].137 * `wiki-macros` - Environment-specific [wiki:TracWikiMacros Wiki macros]. 106 138 107 139 '''Note: don't confuse a Trac environment directory with the source code repository directory.
