First, VisualSVN Server Manager contains two paths, one is the installation path, such as native: C:\Program Files\VisualSVN Server, and the other is the library path, such as native: C:\Repositories, of which the repositories include each project file and project information file, and the important project information files are authz and htpasswd. authz is the directory access control file, and htpasswd is the VisualSVN Server Manager user and password record file
Now, the method of migrating VisualSVN Server Manager is as follows:
For example: Original Server A, VisualSVN Server Manager Current Server B, VisualSVN Server Manager Steps: 1。 Copy the Repositories folder from A to B 2。 Open VisualSVN Server Manager on B 3。 Right-click Repositories and select import existing repository among all tasks 4. Select the project folder in step 1 to import until all the project imports are complete 5。 Replace authz and htpasswd files to make the users and user permissions in VisualSVN Server Manager on Server B the same as before
At this time, I didn't want to add users and assign permissions one by one, and I felt that there was no other way, so I first checked and recorded the size of all the files, and then added users, and saw which file found changes, and then learned the role of authz and htpasswd files, hehe~~~~~~~~~~ |