Changes between Version 6 and Version 7 of TracEnvironment
- Timestamp:
- 19/05/2016 16:30:59 (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracEnvironment
v6 v7 2 2 3 3 [[TracGuideToc]] 4 [[PageOutline ]]4 [[PageOutline(2-5,Contents,pullout)]] 5 5 6 Trac uses a directory structure and a database for storing project data. The directory is referred to as the environment.6 Trac uses a directory structure and a database for storing project data. The directory is referred to as the '''environment'''. 7 7 8 8 == Creating an Environment … … 21 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. 22 22 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.23 - `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//. 24 24 25 25 - Non-ascii environment paths are not supported. 26 27 - Also, it seems that project names with spaces can be problematic for authentication, see [trac:#7163].28 26 29 - 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. 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]. 28 29 {{{#!div style="border: 1pt dotted; margin: 1em" 30 **Caveat:** don't confuse the //Trac environment directory// with the //source code repository directory//. 31 32 This is a common beginners' mistake. 33 It 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. 34 }}} 30 35 31 36 == Database Connection Strings … … 76 81 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, because of Trac's use of unicode. SQL_ASCII also seems to work. 77 82 78 Under some default configurations (Debian) one will haverun the `createuser` and `createdb` scripts as the `postgres` user:83 Under some default configurations (Debian), run the `createuser` and `createdb` scripts as the `postgres` user: 79 84 {{{#!sh 80 85 $ sudo su - postgres -c 'createuser -U postgres -S -D -R -E -P tracuser' … … 139 144 * `site.html` - Method to customize header, footer, and style, described in TracInterfaceCustomization#SiteAppearance. 140 145 141 === Caveat: don't confuse a ''Trac environment directory'' with the ''source code repository directory'' #Caveat142 143 This is a common beginners' mistake.144 It 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.145 146 146 ---- 147 147 See also: TracAdmin, TracBackup, TracIni, TracGuide