Changes between Version 4 and Version 5 of TracRepositoryAdmin
- Timestamp:
- Jul 21, 2024, 5:32:52 PM (7 weeks ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracRepositoryAdmin
v4 v5 4 4 == Quick start #QuickStart 5 5 6 Trac is primarily used as an issue tracking and project planning system, but can also be used to connect to and maintain source code repositories. This page describes the guidelines and caveats when connecting Trac to a repository. 6 7 * Enable the repository connector(s) for the version control system(s) that you will use. 7 8 * Add repositories through the //Repositories// admin page, using `trac-admin` or by editing the `[repositories]` section of [[wiki:TracIni#repositories-section|trac.ini]]. … … 11 12 == Enabling the components 12 13 13 Support for version control systems is provided by optional components distributed with Trac, which are disabled by default //(since 1.0)//. Subversion and Git must be explicitly enabled if you wish to use them.14 Support for version control systems is provided by optional components distributed with Trac, which are disabled by default. Subversion and Git must be explicitly enabled if you wish to use them. 14 15 15 16 The version control systems can be enabled by adding the following to the `[components]` section of your [TracIni#components-section trac.ini], or enabling the components through the //Plugins// admin page. … … 39 40 === Repository Attributes 40 41 41 There are a number of attributes that can be specified for each repository, and additional attributes may be available through plugins. A repository `name` and one of the `alias` or `dir` attributes are mandatory. All others are optional. 42 43 The following attributes are supported: 42 A repository is defined through the attribute `name` and one of the `alias` or `dir` attributes, all other attributes are optional: 44 43 45 44 ||='''Attribute''' =||='''Description''' =|| … … 51 50 ||The text specified in the `description` attribute is displayed below the top-level entry for the repository in the source browser. It supports WikiFormatting. || 52 51 ||`dir` ||\ 53 || The `dir` attribute specifies the location of the repository in the filesystem. The `alias` and `dir` attributes are mutually exclusive. ||52 || Specifies the location of the repository in the filesystem. The `alias` and `dir` attributes are mutually exclusive. || 54 53 ||`hidden` ||\ 55 54 || When set to `true`, the repository is hidden from the repository index page in the source browser. Browsing the repository is still possible, and links referencing the repository remain valid. || 55 ||`name` ||\ 56 || Identifies the version control system used by the repository. This field is mandatory. || 56 57 ||`sync_per_request`||\ 57 58 || When set to `true` the repository will be synchronized on every request (implicit synchronization). This is generally not recommended. See [#Synchronization repository synchronization] for a comparison of explicit and implicit synchronization. The attribute defaults to `false`. || 58 59 ||`type` ||\ 59 || The `type` attribute specifies the version control system used by the repository. Trac provides support for Subversion and Git, and plugins add support for several other systems. If `type` is not specified, it defaults to the value of the `[versioncontrol]` [wiki:TracIni#versioncontrol-default_repository_type-option default_repository_type] option. ||60 || Specifies the version control system used by the repository. Trac provides support for Subversion and Git, and plugins add support for several other systems. If `type` is not specified, it defaults to the value of the `[versioncontrol]` [wiki:TracIni#versioncontrol-default_repository_type-option default_repository_type] option. || 60 61 ||`url` ||\ 61 || The `url` attribute specifies the root URL to be used for checking out from the repository. When specified, a "Repository URL" link is added to the context navigation links in the source browser, that can be copied into the tool used for creating the working copy. || 62 || Specifies the root URL to be used for checking out from the repository. When specified, a "Repository URL" link is added to the context navigation links in the source browser, that can be copied into the tool used for creating the working copy. || 63 64 Additional attributes may be available through plugins. 62 65 63 66 === Scoped Repository … … 274 277 === Git control files missing 275 278 276 If your repository is not brows eable and you find a message in the log that looks like:279 If your repository is not browsable and you find a message in the log that looks like: 277 280 {{{ 278 281 2017-08-08 10:49:17,339 Trac[PyGIT] ERROR: GIT control files missing in '/path/to/git-repository' … … 280 283 }}} 281 284 282 First check that the path to your repository is correct. If the path is correct, you may have a permission problem whereby the web server cannotaccess the repository. You can use Git to verify the repository. On a Debian-like Linux OS, the following command should help:285 First check that the path to your repository is correct. If the path is correct, you may not have the permission to have the web server access the repository. You can use Git to verify the repository. On a Debian-like Linux OS, the following command should help: 283 286 {{{#!sh 284 287 $ sudo -u www-data git --git-dir=/path/to/git-repository fsck