53 | | For some version control systems, it is possible to specify not only the path to the repository in the `dir` attribute, 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. |
| 53 | === Scoped Repository |
| 54 | |
| 55 | For some version control systems, it is possible to specify not only the path to the repository in the `dir` attribute, but also a ''scope'' within the repository. Trac will then only show information related to the files and changesets below that scope. The scope is specified by appending a path that is relative to the repository root. The Subversion backend for Trac supports this. |
| 56 | |
| 57 | For example, assume a repository at filesystem path `/var/svn/repos1` with several directories at the root of the repository: `/proj1`, `/proj2`, etc. The following configuration would scope the repository to `/proj1`: |
| 58 | {{{#!ini |
| 59 | proj1.dir = /var/svn/repos1/proj1 |
| 60 | proj1.type = svn |
| 61 | }}} |
| 62 | |
| 63 | For other repository types, check the corresponding plugin's documentation. |