Recently set up an automated test framework and have a look at the SVN build. For the general use of the scene, VisualSVN is very convenient, and very quick to get started.
Because it is the first demo, later to migrate to other servers above, so you are familiar with the migration of the server. Here are some of the logging information:
VISUALSVN server consists of two paths:
1. Installation path-for example: C:\Program files\visualsvn Server.
2. Library path-for example: D:\KCWL\MySVN\Repositories.
Repositories includes project documents and project information documents. Important project information files are Authz and htpasswd:1) Authz is the Directory access control file, 2) htpasswd is the VISUALSVN Server Manager user and password record file.
Pre-conditions
Original server A,VISUALSVN Server Manager
Current server B,VISUALSVN Server Manager
VISUALSVN Server Migration Basic steps
1. Copy the repositories folder on a to B
2. Open VisualSVN Server Manager on B
3. Right-click Repositories, select Import existing in All Tasks repository
4. Select the project folder in step 1 to import until all projects have been imported to completion
5. Replace the Authz and htpasswd files so that the user and user rights in VISUALSVN Server Manager are consistent with the previous
On Windows, migrate VISUALSVN server