# Changes between Version 1 and Version 2 of TracRepositoryAdmin

Ignore:
Timestamp:
Oct 11, 2015, 11:33:31 AM (6 years ago)
Comment:

--

### Legend:

Unmodified
 v1 ||The dir attribute specifies the location of the repository in the filesystem. It corresponds to the value previously specified in the option [trac] repository_dir. The alias and dir attributes are mutually exclusive. || ||hidden ||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. || ||type ||The type attribute sets the type of version control system used by the repository. Trac supports Subversion out-of-the-box, and plugins add support for many other systems. If type is not specified, it defaults to the value of the [trac] repository_type option. || ||type ||The type attribute sets the type of version control system used by the repository. Trac supports Subversion and Git out-of-the-box, and plugins add support for many other systems. If type is not specified, it defaults to the value of the [trac] repository_type option. || ||url ||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. || === Explicit synchronization === #ExplicitSync This is the preferred method of repository synchronization. It requires setting the [trac]  repository_sync_per_request option in [wiki:TracIni#trac-section trac.ini] to an empty value, and adding a call to trac-admin in the post-commit hook of each repository. Additionally, if a repository allows changing revision metadata, a call to trac-admin must be added to the post-revprop-change hook as well. This is the preferred method of repository synchronization. It requires setting the [trac]  repository_sync_per_request option in [wiki:TracIni#trac-section trac.ini] to an empty value, and adding a call to trac-admin in the post-commit hook of each repository. Additionally, if a repository allows changing revision metadata, a call to trac-admin must be added to the post-revprop-change hook as well. changeset added [...]:: The  argument can be either a repository name (use "(default)" for the default repository) or the path to the repository. Note that you may have to set the environment variable PYTHON_EGG_CACHE to the same value as was used for the web server configuration before calling trac-admin, if you changed it from its default location. See [wiki:TracPlugins Trac Plugins] for more information. Note that you may have to set the environment variable PYTHON_EGG_CACHE to the same value as was used for the web server configuration before calling trac-admin, if you changed it from its default location. See [wiki:TracPlugins Trac Plugins] for more information. ==== Subversion ==== The following examples are complete post-commit and post-revprop-change scripts for Subversion. They should be edited for the specific environment, marked executable (where applicable) and placed in the hooks directory of each repository. On Unix (post-commit): /usr/bin/trac-admin /path/to/env changeset added "$1" "$2" }}} Note: Check with whereis trac-admin, whether trac-admin is really installed under /usr/bin/ or maybe under /usr/local/bin/ and adapt the path. On Windows (post-commit.cmd): {{{#!application/x-dos-batch {{{#!bat @C:\Python26\Scripts\trac-admin.exe C:\path\to\env changeset added "%1" "%2" }}} }}} On Windows (post-revprop-change.cmd): {{{#!application/x-dos-batch {{{#!bat @C:\Python26\Scripts\trac-admin.exe C:\path\to\env changeset modified "%1" "%2" }}} See the [http://svnbook.red-bean.com/en/1.5/svn.reposadmin.create.html#svn.reposadmin.create.hooks section about hooks] in the Subversion book for more information. Other repository types will require different hook setups. Git hooks can be used in the same way for explicit syncing of git repositories. Add the following to .git/hooks/post-commit: {{{#!sh REV=$(git rev-parse HEAD) trac-admin /path/to/env changeset added$REV }}} For Mercurial, add the following entries to the .hgrc file of each repository accessed by Trac (if [trac:TracMercurial] is installed in a Trac plugins directory, download [source:plugins/0.13/mercurial-plugin/tracext/hg/hooks.py hooks.py] and place it somewhere accessible): ==== Git ==== Git hooks can be used in the same way for explicit syncing of Git repositories.  If your git repository is one that gets committed to directly on the machine that hosts trac, add the following to the hooks/post-receive file in your git repo (note: this will do nothing if you only update the repo by pushing to it): {{{#!sh #!/bin/sh REV=$(git rev-parse HEAD) trac-admin /path/to/env changeset added$REV }}} Alternately, if your repository is one that only gets pushed to, add the following to the hooks/post-receive file in the repo: {{{#!sh #!/bin/sh while read oldrev newrev refname; do git rev-list --reverse $newrev ^$oldrev  | \ while read rev; do trac-admin /path/to/env changeset added \$rev done done }}} The  argument can be either a repository name (use "(default)" for the default repository) or the path to the repository. ==== Mercurial ==== For Mercurial, add the following entries to the .hgrc file of each repository accessed by Trac (if [trac:TracMercurial] is installed in a Trac plugins directory, download [trac:source:mercurial-plugin/tracext/hg/hooks.py hooks.py] and place it somewhere accessible): {{{#!ini [hooks] == Migration from a single-repository setup (Mercurial) == #MigrationMercurial The following procedure illustrates a typical migration from a Mercurial single-repository setup to multiple repositories. Please note that at the time of writing, no initial resynchronization or any hooks are necessary for Mercurial repositories - see #9485 for more information. The following procedure illustrates a typical migration from a Mercurial single-repository setup to multiple repositories. Please note that at the time of writing, no initial resynchronization or any hooks are necessary for Mercurial repositories - see [trac:ticket:9485 #9485] for more information. 1. Upgrade to the latest version of the TracMercurial plugin.