Changes between Version 1 and Version 2 of TracEnvironment
- Timestamp:
- 05/10/20 17:24:38 (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracEnvironment
v1 v2 17 17 `trac-admin` will ask you for the name of the project and the [#DatabaseConnectionStrings database connection string]. 18 18 19 A base configuration can be specified using the `--inherit` or `--config` options. The `--inherit` option can be specified one or more times to utilize a [TracIni#GlobalConfiguration global configuration]. The options specified in a `--config` file will be used to override the defaults when initializing `trac.ini`. See below for an [#SourceCodeRepository example] of defining repositories in a configuration file. 20 19 21 === Useful Tips 20 22 21 23 - 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. 22 24 23 - 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. 24 25 - `initenv` does not create a version control repository for the specified path. If you wish to specify a default repository using the optional 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//. 25 - 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. 26 26 27 27 - Non-ascii environment paths are not supported. 28 28 29 - TracPlugins located in a [TracIni#inherit-plugins_dir-option shared plugins directory] that is defined in an [TracIni#GlobalConfiguration inherited configuration] are not enabled by default, in contrast to plugins in the environment `plugins` directory. Hence, if they need to create extra tables, for example, the tables will not be created during environment creation and you'll need to [TracUpgrade#UpgradetheTracEnvironment upgrade the environment]. Alternatively you can avoid the need to upgrade the environment by explicitly enabling the plugin in the inherited configuration, or in a configuration file using the`--config` option. See TracAdmin#FullCommandReference for more information.29 - TracPlugins located in a [TracIni#inherit-plugins_dir-option shared plugins directory] that is defined in an [TracIni#GlobalConfiguration inherited configuration] are not enabled by default, in contrast to plugins in the environment `plugins` directory. Hence, if they need to create extra tables, for example, the tables will not be created during environment creation and you'll need to [TracUpgrade#UpgradetheTracEnvironment upgrade the environment]. Alternatively you can avoid the need to upgrade the environment by explicitly enabling the plugin(s) in a configuration file using the `--inherit` or `--config` option. See TracAdmin#FullCommandReference for more information. 30 30 31 31 {{{#!div style="border: 1pt dotted; margin: 1em;" … … 103 103 }}} 104 104 105 === Changing Database Backend 106 107 The TracAdmin `convert_db` command allows migrating between SQLite, MySQL and PostgreSQL databases. 108 109 [[TracAdminHelp(convert_db)]] 110 111 == Deleting a Trac Environment 112 113 The Trac environment can be deleted using standard filesystem utilities to delete the directory that was passed to the `initenv` command. For an environment using SQLite, this will also delete the SQLite database, which resides on-disk in the environment `db` directory. For an environment using PostgreSQL or MySQL, you will need to use the associated database utilities to delete the database. 114 105 115 == Source Code Repository 106 116 107 A 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. 117 A 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. There are several ways to connect repositories to an environment, see TracRepositoryAdmin. 108 118 109 There are several 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. 119 Repositories can be defined at the time of environment creation by specifying a configuration file to the `initenv` command using the `--config` or `--inherit` options. Cached repositories will be synchronized if the repository connector(s) are enabled. Example: 120 121 {{{#!sh 122 $ trac-admin $ENV initenv --config=config.ini 123 $ cat config.ini 124 [components] 125 tracopt.versioncontrol.* = enabled 126 127 [repositories] 128 .dir = /path/to/default/type/repos 129 repos1.type = git 130 repos1.dir = /path/to/git/repos 131 repos2.type = svn 132 repos2.dir = /path/to/svn/repos 133 }}} 110 134 111 135 == Directory Structure