| 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 | | [repositories] |
| 110 | | .type = svn |
| 111 | | .dir = /path/to/your/repository |
| 112 | | }}} |
| 113 | | |
| 114 | | The configuration for a scoped Subversion repository would be: |
| 115 | | {{{#!ini |
| 116 | | [repositories] |
| 117 | | .type = svn |
| 118 | | .dir = /path/to/your/repository/scope/within/repos |
| 119 | | }}} |
| | 98 | There 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. |
