Edgewall Software

Changes between Version 17 and Version 18 of 1.3/TracRepositoryAdmin


Ignore:
Timestamp:
Jul 16, 2019, 10:26:12 PM (4 months ago)
Author:
Ryan J Ollos
Comment:

Format and add section for Default Repository.

Legend:

Unmodified
Added
Removed
Modified
  • 1.3/TracRepositoryAdmin

    v17 v18  
    2525== Specifying repositories #Repositories
    2626
    27 Trac supports multiple repositories per environment, and the repositories may be for different version control systems. Each repository must be defined in a repository configuration provider, the three supported by default are the [#ReposDatabase database store], the [#ReposTracIni trac.ini configuration file] and the [#ReposGitWeb GitWeb configuration file]. You can define your repositories through a mix of providers, but typically each repository should only be defined in a single provider. At the very least, the names used for each repository must be unique across all providers, otherwise duplicates will be discarded.
     27Trac supports multiple repositories per environment, and the repositories may be for different version control systems. Each repository must be defined in a repository configuration provider. Repository providers included with Trac are the [#ReposDatabase database store], the [#ReposTracIni trac.ini configuration file] and the [#ReposGitWeb GitWeb configuration file]. Additional providers are available as plugins.
     28
     29You can define your repositories through a mix of providers, but each repository should only be defined in a single provider. The repository names must be unique across all providers and duplicate names are discarded.
    2830
    2931It is possible to define aliases of repositories that act as "pointers" to real repositories. This can be useful when renaming a repository, to avoid breaking links to the old name.
     32
     33=== Default Repository
     34
     35Trac's repositories are listed in the Repository Index when navigating to //Browse Source//. The default repository is displayed first, followed by the Repository Index. TracLinks without a repository name in the path specification (e.g. `[1]` rather than `[1/repos1]`) refer to the default repository. !TracLinks for repositories other than the default must include the repository name in the path specification.
     36
     37From the Repository Admin page, the default repository is specified by leaving the //Name// attribute empty. From the command line, the default repository is specified using the string `(default)` or `""`. In TracIni, the default repository is specified by leaving the `{name}` empty for each `{name}.{attribute}` option (e.g. `.dir = /path/to/dir`).
     38
     39=== Repository Attributes
    3040
    3141There 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.
     
    117127Repositories that support caching are cached by default. The Subversion and Git backends support caching. The [trac:TracMercurial Mercurial plugin] does not yet support caching ([trac:#8417]). To disable caching, set the `cached` attribute to `false`.
    118128
    119 After adding a repository, the cache for that repository must be re-synchronized once with the `trac-admin $ENV repository resync` command.
     129After adding a cached repository, the cache must be populated with the `trac-admin $ENV repository resync` command.
    120130
    121131 `repository resync <repos>`::