Making WordPress.org

Changes between Initial Version and Version 1 of TracEnvironment

06/05/13 17:29:27 (5 years ago)



  • TracEnvironment

    v1 v1  
     1= The Trac Environment = 
     3Trac uses a directory structure and a database for storing project data. The directory is referred to as the “environment”. 
     5== Creating an Environment == 
     7A new Trac environment is created using  [TracAdmin#initenv trac-admin's initenv]: 
     9$ trac-admin /path/to/myproject initenv 
     12`trac-admin` will ask you for the name of the project and the 
     13database connection string (explained below). 
     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.  
     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 - Non-ascii environment paths are not supported 
     25 - Also, it seems that project names with spaces can be problematic for authentication (see [trac:#7163]). 
     27 - 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. 
     29== Database Connection Strings == 
     31Since version 0.9, Trac supports both [http://sqlite.org/ SQLite] and 
     32[http://www.postgresql.org/ PostgreSQL] database backends.  Preliminary 
     33support for [http://mysql.com/ MySQL] was added in 0.10.  The default is 
     34to use SQLite, which is probably sufficient for most projects. The database 
     35file is then stored in the environment directory, and can easily be  
     36[wiki:TracBackup backed up] together with the rest of the environment. 
     38=== SQLite Connection String === 
     39The connection string for an SQLite database is: 
     43where `db/trac.db` is the path to the database file within the Trac environment. 
     45=== PostgreSQL Connection String === 
     46If you want to use PostgreSQL or MySQL instead, you'll have to use a 
     47different connection string. For example, to connect to a PostgreSQL 
     48database on the same machine called `trac`, that allows access to the 
     49user `johndoe` with the password `letmein`, use: 
     53''Note that due to the way the above string is parsed, the "/" and "@" characters cannot be part of the password.'' 
     55If PostgreSQL is running on a non-standard port (for example 9342), use: 
     60On UNIX, you might want to select a UNIX socket for the transport, 
     61either the default socket as defined by the PGHOST environment variable: 
     65or a specific one: 
     70Note that with PostgreSQL you will have to create the database before running 
     71`trac-admin initenv`. 
     73See the [http://www.postgresql.org/docs/ PostgreSQL documentation] for detailed instructions on how to administer [http://postgresql.org PostgreSQL]. 
     74Generally, the following is sufficient to create a database user named `tracuser`, and a database named `trac`. 
     76createuser -U postgres -E -P tracuser 
     77createdb -U postgres -O tracuser -E UTF8 trac 
     79When 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. 
     81Under some default configurations (debian) one will have run the `createuser` and `createdb` scripts as the `postgres` user.  For example: 
     83sudo su - postgres -c 'createuser -U postgres -S -D -R -E -P tracuser' 
     84sudo su - postgres -c 'createdb -U postgres -O tracuser -E UTF8 trac' 
     87Trac uses the `public` schema by default but you can specify a different schema in the connection string: 
     92=== MySQL Connection String === 
     94If you want to use MySQL instead, you'll have to use a 
     95different connection string. For example, to connect to a MySQL 
     96database on the same machine called `trac`, that allows access to the 
     97user `johndoe` with the password `letmein`, the mysql connection string is: 
     102== Source Code Repository == 
     104Since 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`). 
     106In 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. 
     107You can also explicitly disable the `trac.versioncontrol.*` components (which are otherwise still loaded) 
     110trac.versioncontrol.* = disabled 
     113For some version control systems, it is possible to specify not only the path to the repository, 
     114but also a ''scope'' within the repository. Trac will then only show information 
     115related to the files and changesets below that scope. The Subversion backend for 
     116Trac supports this; for other types, check the corresponding plugin's documentation. 
     118Example of a configuration for a Subversion repository used as the default repository: 
     121repository_type = svn 
     122repository_dir = /path/to/your/repository 
     125The configuration for a scoped Subversion repository would be: 
     128repository_type = svn 
     129repository_dir = /path/to/your/repository/scope/within/repos 
     132== Directory Structure == 
     134An environment directory will usually consist of the following files and directories: 
     136 * `README` - Brief description of the environment. 
     137 * `VERSION` - Contains the environment version identifier. 
     138 * `attachments` - Attachments to wiki pages and tickets are stored here. 
     139 * `conf` 
     140   * `trac.ini` - Main configuration file. See TracIni. 
     141 * `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 
     149=== Caveat: don't confuse a ''Trac environment directory'' with the ''source code repository directory'' #Caveat 
     151This is a common beginners' mistake. 
     152It happens that the structure for a Trac environment is loosely modelled after the Subversion repository directory  
     153structure, but those are two disjoint entities and they are not and ''must not'' be located at the same place. 
     156See also: TracAdmin, TracBackup, TracIni, TracGuide