191 | | == Migration from a single-repository setup (Subversion) #Migration |
192 | | The following procedure illustrates a typical migration from a Subversion single-repository setup to multiple repositories. |
193 | | |
194 | | 1. Remove the default repository specification from the `[trac] repository_dir` option. |
195 | | 1. Add the main repository as a named repository. |
196 | | 1. Re-synchronize the main repository. |
197 | | 1. Set up post-commit and post-revprop-change hooks on the "main" repository, and set the repository's `sync_per_request` attribute to `false`. |
198 | | 1. Add an alias to the main repository as the default repository (by leaving out the the `name`, e.g. `.alias = main`). This ensures that all links predating the migration still resolve to the main repository. |
199 | | 1. Repeat steps 2, 3 and 4 to add other "named" repositories as needed. |
200 | | |
201 | | == Migration from a single-repository setup (Mercurial) #MigrationMercurial |
202 | | 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. |
203 | | |
204 | | 1. Upgrade to the latest version of the [trac:TracMercurial] plugin. |
205 | | 1. Remove the default repository specification from the `[trac] repository_dir` option. |
206 | | 1. Add the main repository as a named repository. |
207 | | 1. Add an alias to the main repository as the default repository (by leaving out the the `name`, e.g. `.alias = main`). This ensures that all links predating the migration still resolve to the main repository. |
208 | | 1. Repeat step 3 to add other "named" repositories as needed. |
209 | | |