Edgewall Software

Changes between Initial Version and Version 1 of 1.1/TracEnvironment

Nov 24, 2014, 12:23:34 PM (6 years ago)
Ryan J Ollos

Copied from TracEnvironment@58.


  • 1.1/TracEnvironment

    v1 v1  
     1= The Trac Environment
     5Trac uses a directory structure and a database for storing project data. The directory is referred to as the “environment”.
     7== Creating an Environment
     9A new Trac environment is created using  [TracAdmin#initenv trac-admin's initenv]:
     11$ trac-admin /path/to/myproject initenv
     14`trac-admin` will ask you for the name of the project and the
     15database connection string (explained below).
     17=== Some Useful Tips
     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).
     21 - The user under which the web server runs will require file system write permission to
     22 the environment directory and all the files inside. Please remember to set
     23 the appropriate permissions. The same applies to the source code repository,
     24 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.
     26 - `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.
     28 - Non-ascii environment paths are not supported
     30 - Also, it seems that project names with spaces can be problematic for authentication (see [trac:#7163]).
     32 - 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.
     34== Database Connection Strings
     36Trac supports [http://sqlite.org/ SQLite], [http://www.postgresql.org/ PostgreSQL] and [http://mysql.com/ MySQL] database backends.  The default is to use SQLite, which is probably sufficient for most projects. The database
     37file is then stored in the environment directory, and can easily be
     38[wiki:TracBackup backed up] together with the rest of the environment.
     40Note that if the username or password of the connection string (if applicable) contains the `:`, `/` or `@` characters, they need to be URL encoded.
     42=== SQLite Connection String
     43The connection string for an SQLite database is:
     47where `db/trac.db` is the path to the database file within the Trac environment.
     49=== PostgreSQL Connection String
     50If you want to use PostgreSQL or MySQL instead, you'll have to use a
     51different connection string. For example, to connect to a PostgreSQL
     52database on the same machine called `trac`, that allows access to the
     53user `johndoe` with the password `letmein`, use:
     58If PostgreSQL is running on a non-standard port (for example 9342), use:
     63On UNIX, you might want to select a UNIX socket for the transport,
     64either the default socket as defined by the PGHOST environment variable:
     68or a specific one:
     73Note that with PostgreSQL you will have to create the database before running
     74`trac-admin initenv`.
     76See the [http://www.postgresql.org/docs/ PostgreSQL documentation] for detailed instructions on how to administer [http://postgresql.org PostgreSQL].
     77Generally, the following is sufficient to create a database user named `tracuser`, and a database named `trac`.
     79$ createuser -U postgres -E -P tracuser
     80$ createdb -U postgres -O tracuser -E UTF8 trac
     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 trac's use of unicode in trac.  SQL_ASCII also seems to work.
     84Under some default configurations (debian) one will have run the `createuser` and `createdb` scripts as the `postgres` user.  For example:
     86$ sudo su - postgres -c 'createuser -U postgres -S -D -R -E -P tracuser'
     87$ sudo su - postgres -c 'createdb -U postgres -O tracuser -E UTF8 trac'
     90Trac uses the `public` schema by default but you can specify a different schema in the connection string:
     95=== MySQL Connection String
     97The format of the MySQL connection string is similar to the examples presented for PostgreSQL, with the `postgres` scheme being replaced by `mysql`. For example, to connect to a MySQL
     98database on the same machine called `trac`, allowing access to the
     99user `johndoe` with the password `letmein`, the mysql connection string is:
     104== Source Code Repository
     106Since 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`).
     108In 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.
     109You can also explicitly disable the `trac.versioncontrol.*` components (which are otherwise still loaded)
     112trac.versioncontrol.* = disabled
     115For some version control systems, it is possible to specify not only the path to the repository,
     116but also a ''scope'' within the repository. Trac will then only show information
     117related to the files and changesets below that scope. The Subversion backend for
     118Trac supports this; for other types, check the corresponding plugin's documentation.
     120Example of a configuration for a Subversion repository used as the default repository:
     123repository_type = svn
     124repository_dir = /path/to/your/repository
     127The configuration for a scoped Subversion repository would be:
     130repository_type = svn
     131repository_dir = /path/to/your/repository/scope/within/repos
     134== Directory Structure
     136An environment directory will usually consist of the following files and directories:
     138 * `README` - Brief description of the environment.
     139 * `VERSION` - Contains the environment version identifier.
     140 * `attachments` - Attachments to wiki pages and tickets are stored here.
     141 * `conf`
     142  * `trac.ini` - Main configuration file. See TracIni.
     143 * `db`
     144  * `trac.db` - The SQLite database (if you're using SQLite).
     145 * `htdocs` - directory containing web resources, which can be referenced in Genshi templates using `/htdocs/site/...` URLs.
     146 * `log` - default directory for log files, if logging is turned on and a relative path is given.
     147 * `plugins` - Environment-specific [wiki:TracPlugins plugins]
     148 * `templates` - Custom Genshi environment-specific templates.
     149  * `site.html` - method to customize header, footer, and style, described in TracInterfaceCustomization#SiteAppearance
     151=== Caveat: don't confuse a ''Trac environment directory'' with the ''source code repository directory'' #Caveat
     153This is a common beginners' mistake.
     154It happens that the structure for a Trac environment is loosely modelled after the Subversion repository directory
     155structure, but those are two disjoint entities and they are not and ''must not'' be located at the same place.
     158See also: TracAdmin, TracBackup, TracIni, TracGuide