Changes between Version 1 and Version 2 of TracEnvironment


Ignore:
Timestamp:
Dec 3, 2016, 9:48:27 PM (8 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TracEnvironment

    v1 v2  
    11= The Trac Environment
     2
    23[[TracGuideToc]]
    3 [[PageOutline]]
     4[[PageOutline(2-5,Contents,pullout)]]
    45
    56Trac uses a directory structure and a database for storing project data. The directory is referred to as the environment.
     7Trac uses a directory structure and a database for storing project data. The directory is referred to as the '''environment'''.
     8
     9Trac supports [http://sqlite.org/ SQLite], [http://www.postgresql.org/ PostgreSQL] and [http://mysql.com/ MySQL] databases. With PostgreSQL and MySQL you have to create the database before running `trac-admin initenv`.
    610
    711== Creating an Environment
    812
    9 A new Trac environment is created using [TracAdmin#initenv trac-admin's initenv]:
     13A new Trac environment is created using the [TracAdmin#initenv initenv] command:
    1014{{{#!sh
    1115$ trac-admin /path/to/myproject initenv
    1216}}}
    1317
    14 `trac-admin` will ask you for the name of the project and the database connection string, see below.
     18`trac-admin` will ask you for the name of the project and the [#DatabaseConnectionStrings database connection string].
    1519
    1620=== Useful Tips
    … …  
    1822 - 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.
    1923
    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.
     24 - 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.
    2425 
    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.
     26 - `initenv` does not create a version control repository for the specified path. If you wish to specify a default repository using optional the arguments to `initenv` you must create the repository first, otherwise you will see a message when initializing the environment: //Warning: couldn't index the default repository//.
    2627
    2728 - Non-ascii environment paths are not supported.
    28  
    29  - Also, it seems that project names with spaces can be problematic for authentication, see [trac:#7163].
    3029
    31  - 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.
     30 - TracPlugins located in a [TracIni#inherit-section shared plugins folder] that is defined in an [TracIni#GlobalConfiguration inherited configuration] are not loaded during creation, and hence, if they need to create extra tables for example, you'll need to [TracUpgrade#UpgradetheTracEnvironment upgrade the environment]. Alternatively you can avoid the need to upgrade the environment by specifying a configuration file at the time the environment is created, using the `--config` option. See TracAdmin#FullCommandReference for more information.
     31
     32{{{#!div style="border: 1pt dotted; margin: 1em"
     33**Caveat:** don't confuse the //Trac environment directory// with the //source code repository directory//.
     34
     35This is a common beginners' mistake.
     36It happens that the structure for a Trac environment is loosely modeled 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.
     37}}}
    3238
    3339== Database Connection Strings
    3440
    35 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.
     41You will need to specify a database connection string at the time the environment is created. The default is SQLite, which is probably sufficient for most projects. The SQLite database file is stored in the environment directory, and can easily be [wiki:TracBackup backed up] together with the rest of the environment.
    3642
    3743Note that if the username or password of the connection string (if applicable) contains the `:`, `/` or `@` characters, they need to be URL encoded.
    3844
    3945=== SQLite Connection String
     46
    4047The connection string for an SQLite database is:
    4148{{{
    … …  
    4552
    4653=== PostgreSQL Connection String
    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:
     54
     55The connection string for PostgreSQL is a bit more complex. For example, to connect to a PostgreSQL database named `trac` on `localhost` for user `johndoe` and password `letmein`, use:
    4856{{{
    4957postgres://johndoe:letmein@localhost/trac
    … …  
    5967postgres://user:password@/database
    6068}}}
     69
    6170or a specific one:
    6271{{{
    6372postgres://user:password@/database?host=/path/to/socket/dir
    6473}}}
    65 
    66 Note that with PostgreSQL you will have to create the database before running `trac-admin initenv`.
    6774
    6875See the [http://www.postgresql.org/docs/ PostgreSQL documentation] for detailed instructions on how to administer [http://postgresql.org PostgreSQL].
    … …  
    7279$ createdb -U postgres -O tracuser -E UTF8 trac
    7380}}}
    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.
    7581
    76 Under some default configurations (debian) one will have run the `createuser` and `createdb` scripts as the `postgres` user.  For example:
     82When 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.
     83
     84Under some default configurations (Debian), run the `createuser` and `createdb` scripts as the `postgres` user:
    7785{{{#!sh
    7886$ sudo su - postgres -c 'createuser -U postgres -S -D -R -E -P tracuser'
    … …  
    8795=== MySQL Connection String
    8896
    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:
     97The 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 `localhost` named `trac` for user `johndoe` with password `letmein`:
    9098{{{
    9199mysql://johndoe:letmein@localhost:3306/trac
    … …  
    94102== Source Code Repository
    95103
    96 Since 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`.
     104A single environment can be connected to more than one repository. However, by default Trac is not connected to any source code repository, and the ''Browse Source'' navigation item will not be displayed.
    97105
    98 In 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.
    100 {{{#!ini
    101 [components]
    102 trac.versioncontrol.* = disabled
    103 }}}
    104 
    105 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.
    106 
    107 Example of a configuration for a Subversion repository used as the default repository:
    108 {{{#!ini
    109 [trac]
    110 repository_type = svn
    111 repository_dir = /path/to/your/repository
    112 }}}
    113 
    114 The configuration for a scoped Subversion repository would be:
    115 {{{#!ini
    116 [trac]
    117 repository_type = svn
    118 repository_dir = /path/to/your/repository/scope/within/repos
    119 }}}
     106There are many different ways to connect repositories to an environment, see TracRepositoryAdmin. A single repository can be specified when the environment is created by passing the optional arguments `repository_type` and `repository_dir` to the `initenv` command.
    120107
    121108== Directory Structure
    122109
    123 An environment directory will usually consist of the following files and directories:
     110An environment consists of the following files and directories:
    124111
    125112 * `README` - Brief description of the environment.
    126113 * `VERSION` - Environment version identifier.
    127  * `attachments` - Attachments to wiki pages and tickets are stored here.
     114 * `files`
     115  * `attachments` - Attachments to wiki pages and tickets.
    128116 * `conf`
    129117  * `trac.ini` - Main configuration file. See TracIni.
    130118 * `db`
    131119  * `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.
     120 * `htdocs` - Directory containing web resources, which can be referenced in Genshi templates using `/chrome/site/...` URLs.
     121 * `log` - Default directory for log files, if `file` logging is enabled and a relative path is given.
    134122 * `plugins` - Environment-specific [wiki:TracPlugins plugins].
    135123 * `templates` - Custom Genshi environment-specific templates.
    136124  * `site.html` - Method to customize header, footer, and style, described in TracInterfaceCustomization#SiteAppearance.
    137125
    138 === Caveat: don't confuse a ''Trac environment directory'' with the ''source code repository directory'' #Caveat
    139 
    140 This 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.
    143 
    144126----
    145127See also: TracAdmin, TracBackup, TracIni, TracGuide