Changes between Version 4 and Version 5 of TracEnvironment


Ignore:
Timestamp:
2016-01-09T17:05:34+01:00 (9 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TracEnvironment

    v4 v5  
    11= The Trac Environment
     2
    23[[TracGuideToc]]
    34[[PageOutline]]
    … …  
    1819 - 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.
    1920
    20  - The user under which the web server runs will require file system write permission to
    21  the environment directory and all the files inside. Please remember to set
    22  the appropriate permissions. The same applies to the source code repository,
    23  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.
     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.
    2422 
    25  - `initenv`, when using an svn repository, does not imply that trac-admin will perform `svnadmin create` for the specified repository path. You need to perform the `svnadmin create` prior to `trac-admin initenv` if you're creating a new svn repository altogether with a new trac environment, otherwise you will see a message "Warning: couldn't index the repository" when initializing the environment.
     23 - `initenv`, when using an svn repository, does not imply that trac-admin will perform `svnadmin create` for the specified repository path. You need to perform the `svnadmin create` prior to `trac-admin initenv` if you're creating a new svn repository altogether with a new Trac environment; otherwise you will see a message "Warning: couldn't index the repository" when initializing the environment.
    2624
    2725 - Non-ascii environment paths are not supported.
    … …  
    3836
    3937=== SQLite Connection String
     38
    4039The connection string for an SQLite database is:
    4140{{{
    … …  
    4544
    4645=== PostgreSQL Connection String
     46
    4747If 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:
    4848{{{
    … …  
    5959postgres://user:password@/database
    6060}}}
     61
    6162or a specific one:
    6263{{{
    … …  
    7273$ createdb -U postgres -O tracuser -E UTF8 trac
    7374}}}
    74 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.
    7575
    76 Under some default configurations (debian) one will have run the `createuser` and `createdb` scripts as the `postgres` user.  For example:
     76When 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
     78Under some default configurations (Debian) one will have run the `createuser` and `createdb` scripts as the `postgres` user:
    7779{{{#!sh
    7880$ sudo su - postgres -c 'createuser -U postgres -S -D -R -E -P tracuser'
    … …  
    8789=== MySQL Connection String
    8890
    89 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`, the MySQL connection string is:
     91The 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`:
    9092{{{
    9193mysql://johndoe:letmein@localhost:3306/trac
    … …  
    9799
    98100In Trac 0.12 `trac-admin` no longer asks questions related to repositories. Therefore, by default Trac is not connected to any source code repository, and the ''Browse Source'' toolbar item will not be displayed.
    99 You can also explicitly disable the `trac.versioncontrol.*` components, which are otherwise still loaded.
     101You can also explicitly disable the `trac.versioncontrol.*` components, which are otherwise still loaded:
    100102{{{#!ini
    101103[components]
    … …  
    125127 * `README` - Brief description of the environment.
    126128 * `VERSION` - Environment version identifier.
    127  * `attachments` - Attachments to wiki pages and tickets are stored here.
     129 * `files`
     130  * `attachments` - Attachments to wiki pages and tickets.
    128131 * `conf`
    129132  * `trac.ini` - Main configuration file. See TracIni.
    130133 * `db`
    131134  * `trac.db` - The SQLite database, if you are using SQLite.
    132  * `htdocs` - Directory containing web resources, which can be referenced in Genshi templates using `/htdocs/site/...` URLs.
    133  * `log` - Default directory for log files, if logging is turned on and a relative path is given.
     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.
    134137 * `plugins` - Environment-specific [wiki:TracPlugins plugins].
    135138 * `templates` - Custom Genshi environment-specific templates.
    … …  
    139142
    140143This is a common beginners' mistake.
    141 It happens that the structure for a Trac environment is loosely modelled after the Subversion repository directory
    142 structure, but those are two disjoint entities and they are not and ''must not'' be located at the same place.
     144It happens that the structure for a Trac environment is loosely modelled after the Subversion repository directory structure, but those are two disjoint entities and they are not and ''must not'' be located at the same place.
    143145
    144146----