Changes between Version 10 and Version 11 of TracEnvironment


Ignore:
Timestamp:
08/08/15 13:07:49 (2 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracEnvironment

    v10 v11  
    1 = The Trac Environment = 
     1= The Trac Environment 
    22 
    3 Trac uses a directory structure and a database for storing project data. The directory is referred to as the “environment”. 
     3[[TracGuideToc]] 
     4[[PageOutline]] 
    45 
    5 == Creating an Environment == 
     6Trac uses a directory structure and a database for storing project data. The directory is referred to as the environment. 
    67 
    7 A new Trac environment is created using  [TracAdmin#initenv trac-admin's initenv]: 
    8 {{{ 
     8== Creating an Environment 
     9 
     10A new Trac environment is created using [TracAdmin#initenv trac-admin's initenv]: 
     11{{{#!sh 
    912$ trac-admin /path/to/myproject initenv 
    1013}}} 
    1114 
    12 `trac-admin` will ask you for the name of the project and the 
    13 database connection string (explained below). 
     15`trac-admin` will ask you for the name of the project and the database connection string, see below. 
    1416 
    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  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.  
     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.  
    2022  
    21  - `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. 
    2224 
    23  - Non-ascii environment paths are not supported 
     25 - Non-ascii environment paths are not supported. 
    2426  
    25  - Also, it seems that project names with spaces can be problematic for authentication (see [trac:#7163]). 
     27 - Also, it seems that project names with spaces can be problematic for authentication, see [trac:#7163]. 
    2628 
    2729 - TracPlugins located in a [TracIni#inherit-section shared plugins folder] that is defined in an [TracIni#GlobalConfiguration inherited configuration] are currently not loaded during creation, and hence, if they need to create extra tables for example, you'll need to [TracUpgrade#UpgradetheTracEnvironment upgrade the environment] before being able to use it. 
    2830 
    29 == Database Connection Strings == 
     31== Database Connection Strings 
    3032 
    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. 
     33Trac 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. 
    3734 
    38 === SQLite Connection String === 
     35Note that if the username or password of the connection string (if applicable) contains the `:`, `/` or `@` characters, they need to be URL encoded. 
     36 
     37=== SQLite Connection String 
     38 
    3939The connection string for an SQLite database is: 
    4040{{{ 
     
    4343where `db/trac.db` is the path to the database file within the Trac environment. 
    4444 
    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 
     47If 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: 
    5048{{{ 
    5149postgres://johndoe:letmein@localhost/trac 
    5250}}} 
    53 ''Note that due to the way the above string is parsed, the "/" and "@" characters cannot be part of the password.'' 
    5451 
    55 If PostgreSQL is running on a non-standard port (for example 9342), use: 
     52If PostgreSQL is running on a non-standard port, for example 9342, use: 
    5653{{{ 
    5754postgres://johndoe:letmein@localhost:9342/trac 
    5855}}} 
    5956 
    60 On UNIX, you might want to select a UNIX socket for the transport, 
    61 either the default socket as defined by the PGHOST environment variable: 
     57On UNIX, you might want to select a UNIX socket for the transport, either the default socket as defined by the PGHOST environment variable: 
    6258{{{ 
    6359postgres://user:password@/database 
    6460}}} 
     61 
    6562or a specific one: 
    6663{{{ 
     
    6865}}} 
    6966 
    70 Note that with PostgreSQL you will have to create the database before running 
    71 `trac-admin initenv`. 
     67Note that with PostgreSQL you will have to create the database before running `trac-admin initenv`. 
    7268 
    7369See the [http://www.postgresql.org/docs/ PostgreSQL documentation] for detailed instructions on how to administer [http://postgresql.org PostgreSQL]. 
    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' 
     70Generally, 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 
    8574}}} 
    8675 
    87 Trac uses the `public` schema by default but you can specify a different schema in the connection string: 
     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: 
     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 
     84Trac uses the `public` schema by default, but you can specify a different schema in the connection string: 
    8885{{{ 
    8986postgres://user:pass@server/database?schema=yourschemaname 
    9087}}} 
    9188 
    92 === MySQL Connection String === 
     89=== MySQL Connection String 
    9390 
    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: 
     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`: 
    9892{{{ 
    9993mysql://johndoe:letmein@localhost:3306/trac 
    10094}}} 
    10195 
    102 == Source Code Repository == 
     96== Source Code Repository 
    10397 
    104 Since version 0.12, a single Trac environment can be connected to more than one repository. There are many different ways to connect repositories to an environment, see TracRepositoryAdmin. This page also details the various attributes that can be set for a repository (like `type`, `url`, `description`). 
     98Since Trac 0.12, a single environment can be connected to more than one repository. There are many different ways to connect repositories to an environment, see TracRepositoryAdmin. This page also details the various attributes that can be set for a repository, such as `type`, `url`, `description`. 
    10599 
    106100In 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. 
    107 You can also explicitly disable the `trac.versioncontrol.*` components (which are otherwise still loaded) 
    108 {{{ 
     101You can also explicitly disable the `trac.versioncontrol.*` components, which are otherwise still loaded: 
     102{{{#!ini 
    109103[components] 
    110104trac.versioncontrol.* = disabled 
    111105}}} 
    112106 
    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. 
     107For 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. 
    117108 
    118109Example of a configuration for a Subversion repository used as the default repository: 
    119 {{{ 
     110{{{#!ini 
    120111[trac] 
    121112repository_type = svn 
     
    124115 
    125116The configuration for a scoped Subversion repository would be: 
    126 {{{ 
     117{{{#!ini 
    127118[trac] 
    128119repository_type = svn 
     
    130121}}} 
    131122 
    132 == Directory Structure == 
     123== Directory Structure 
    133124 
    134125An environment directory will usually consist of the following files and directories: 
    135126 
    136127 * `README` - Brief description of the environment. 
    137  * `VERSION` - Contains the environment version identifier. 
    138  * `attachments` - Attachments to wiki pages and tickets are stored here. 
     128 * `VERSION` - Environment version identifier. 
     129 * `files` 
     130  * `attachments` - Attachments to wiki pages and tickets. 
    139131 * `conf` 
    140    * `trac.ini` - Main configuration file. See TracIni. 
     132  * `trac.ini` - Main configuration file. See TracIni. 
    141133 * `db` 
    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. 
    148140 
    149141=== Caveat: don't confuse a ''Trac environment directory'' with the ''source code repository directory'' #Caveat 
    150142 
    151143This is a common beginners' mistake. 
    152 It happens that the structure for a Trac environment is loosely modelled after the Subversion repository directory  
    153 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. 
    154145 
    155146----