Changes between Version 2 and Version 3 of TracRepositoryAdmin
- Timestamp:
- Jul 8, 2010, 11:32:44 AM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracRepositoryAdmin
v2 v3 130 130 131 131 132 == Migration from a single-repository setup == #Migration133 The following procedure illustrates a typical migration from a single-repository setup to multiple repositories.132 == Migration from a single-repository setup (Subversion) == #Migration 133 The following procedure illustrates a typical migration from a Subversion single-repository setup to multiple repositories. 134 134 135 135 1. Remove the default repository specification from the `[trac] repository_dir` option. … … 140 140 1. Repeat steps 2, 3 and 4 to add other (named) repositories as needed. 141 141 142 == Migration from a single-repository setup (Mercurial) == #MigrationMercurial 143 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. 144 145 1. Upgrade to the latest version of the TracMercurial plugin. 146 1. Remove the default repository specification from the `[trac] repository_dir` option. 147 1. Add the "main" repository as a named repository. 148 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. 149 1. Repeat step 2 to add other (named) repositories as needed. 150 142 151 == Troubleshooting == 143 152