Manage Repository Folder Hierarchy

Sublime allows repositories to be stored in a flexible folder hierarchy. This enables repositories to be organized and grouped together as you see fit. The folder a repository is in will determine the repository URL as well as how it can be found in the Sublime web interface.

For example, if you have a folder called Projects, repositories stored in that folder will have a URL of svn://myserver/Projects/myrepository.

If the Projects folder contains a subfolder called Billable, repositories stored in the Billable folder will have a URL of svn://myserver/Projects/Billable/myrepository.

Creating your folder hierarchy is typically one of the first-time configuration activities you will do. However, you can always change this later.

Note: If you are using LDAP Authentication with Apache, creating sub-folders also requires you to configure Apache for these sub-folders. Until you do that, your users will not be able to access repositories located in sub-folders.

Creating the Folder Hierarchy

To create your initial folder hierarchy, simply open your repositories folder using Windows Explorer (C:\Program Files\Sublime\Repositories by default). With that folder open, simply create new folders for your repositories to be stored in. You can see that the folder hierarchy in Sublime will match the folder hierarchy you create here.

Folder Hierarchy

Once you have finished creating folders, you should restart IIS by opening a command prompt and executing the following command:

C:\> iisreset

Moving or Renaming Folders

If you need to move, or rename folders in your hierarchy, or you want to move repositories from one folder to another, you should follow these steps:

  1. Take your server offline from the Administration Home page. This will ensure no users are trying to commit while you are changing folders.
  2. Open up your Repositories folder in Windows Explorer.
  3. In windows explorer, go ahead and rename your folders, create additional folders, or move repositories to new folders.
  4. Reset IIS by opening a command prompt and entering iisreset.
  5. Bring the server back online from the Administration Home screen.
  6. Communicate the changes to your users. Your users should then perform the relocate operation for each repository whose path has changed.