Importing Existing Repositories

You can import your existing repositories into Sublime by simply copying the repository into the Repositories directory on your Sublime server. However, there are a few things you should keep in mind when doing this. If you have customized your repository permissions in your authz or svnserve.conf files, you may need to replicate these settings in the Sublime interface.

This topic will show you how to import a repository, and then cover the gotchas that may arise.

Importing a Repository

To import an existing repository, simply copy the repository folder from the existing server into the Repositories folder for Sublime. If you have customized the repository path, the location may be different.

Once you have copied the repository, open the Sublime web interface and complete the following steps:

  1. Locate the new repository in the folder hierarchy. If you don’t see it, you may need to reset IIS to clear the cache.
  2. Click the repository to be taken to the repository summary screen.
  3. In the Users section of the screen, if you see “Unknown User”, that means that a username exists for this repository that has not yet been added to Sublime. You should add the appropriate users in the user management page before proceeding.
  4. Click the Edit Repository Settings link
  5. Select an owner for the repository.
  6. Click the Permissions tab and review security settings. You may add or remove users at this point and change anonymous access settings.
  7. Click Save

That’s it. Your repository has now been imported and can be managed by Sublime.

Considerations and Gotchas

Extensive Security Customization

Subversion offers a number of security configuration options that are not currently supported by Sublime. Aliases and groups are two examples. If you require these features, you may not want to import your repositories into Sublime. Alternatively, you can import the repository, but never edit security settings for the repository.

Path-based Security

Sublime does not support path-based security within a repository. If you have path-based security configured within your existing authz file, you may not want to import it into Sublime. Alternatively, you can import it, but never edit security settings for the repository.

Hooks

If you choose to use email notifications, Sublime will install its own post-commit hook file. If you already have hooks in place and want to preserve them, you should not enable email notification.