Changes between Version 6 and Version 7 of 0.12/TracRepositoryAdmin
- Timestamp:
- Feb 3, 2010, 12:08:08 AM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
0.12/TracRepositoryAdmin
v6 v7 7 7 * Set up a call to `trac-admin $ENV changeset added $REPO $REV` in the post-commit hook of each repository. Additionally, add a call to `trac-admin $ENV changeset modified $REPO $REV` in the post-revprop-change hook of repositories allowing revision property changes. 8 8 * Set the `[trac] repository_sync_per_request` option to an empty value to disable per-request syncing. 9 9 10 10 11 == Specifying repositories == … … 28 29 29 30 The `name` attribute and one of `alias` or `dir` are mandatory. All others are optional. 31 32 After adding a repository, the cache for that repository must be re-synchronized once with the `trac-admin $ENV repository resync` command. 33 34 `repository resync <repos>`:: 35 Re-synchronize Trac with a repository. 36 30 37 31 38 === In `trac.ini` === … … 70 77 Set the attribute `<key>` to `<value>` for the repository `<repos>`. 71 78 72 Note that the default repository has an empty name, so it will likely need to be quoted when running `trac-admin` from a shell. Alternatively, the name `(default)` can be used instead, for example when running `trac-admin` in interactive mode. 79 Note that the default repository has an empty name, so it will likely need to be quoted when running `trac-admin` from a shell. Alternatively, the name "`(default)`" can be used instead, for example when running `trac-admin` in interactive mode. 80 73 81 74 82 == Repository synchronization … … 86 94 The `<repos>` argument can be either a repository name (use "`(default)`" for the default repository) or the path to the repository. 87 95 88 The following example is a complete post-commit script for Subversion on Unix. It should marked executable and placed in the `hooks` directory of the repository, with the file name `post-commit`.96 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`): 89 97 {{{ 90 98 #!sh … … 98 106 }}} 99 107 100 The post-revprop-change hook for Subversion is very similar. On Unix :108 The post-revprop-change hook for Subversion is very similar. On Unix (`post-revprop-change`): 101 109 {{{ 102 110 #!sh … … 118 126 119 127 128 == Migration from a single-repository setup == 129 The following procedure illustrates a typical migration from a single-repository setup to multiple repositories. 130 131 1. Remove the default repository specification from the `[trac] repository_dir` option. 132 1. Add the "main" repository as a named repository. 133 1. Re-synchronize the main repository. 134 1. Set up post-commit and post-revprop-change hooks on the main repository, and set `[trac] repository_sync_per_request` to an empty value. 135 1. Add a hidden alias to the main repository as the default repository. This ensures that all links predating the migration still resolve to the main repository. 136 1. Repeat steps 2, 3 and 4 to add other (named) repositories as needed. 137 120 138 {{{#!div style="background: #eee; padding: 1px 2em" 121 139 === Editing Notes ===
