Working with SVN

Record the svn server setup and usage process, so that you do not forget it again next time.

1. Install the latest version of subversion, 1.4.5 currently

2. Create a version library root directory, such as D:/svnrepos (the version library directory of all projects uses this as the parent directory)

3. Select the database creation method. Each project has one version of the database (the version is independent, which is used here) and one version of multiple projects (such as comparing related projects)
In this way, you can create a project demo (project name) version library under the D:/svnrepos directory.
> Svnserve create prjdemo

4. Run subversion as a Windows service and use the SC CREATE Command, as shown in figure
SC create svnserve binpath = "\" E: \ subversion \ bin \ svnserve.exe \ "-- service -- root D: /svnrepos "displayname =" Subversion "depend = TCPIP start = auto OBJ =" nt authority \ LocalService"
Run the service for the first time (automatically run later):> Net start Subversion

5. Set the user and permission control for the specific version library, such as the prjdemo project, in the D:/svnreposprjdemo/conf directory.

6. Create and import the basic trunk, tags, and branches directories of SVN for the project version library, such as the prjdemo project:
Create a local folder that contains the preceding three directories. Use the import command to import or use tortoisesvn to import
Note: For cloud on the "SVN write-lock error", delete the service created in Step 4 (SC Delete svnserve) and run OBJ =... delete the cloud, and then execute

8. Create an initial ignore list (ignore-list), check the content of the trunk directory on the server to a local location, and create an ignore list for a specific file type.
This step can also be placed after Step 7, check out the import project, and then create

7. import the local project locally :\.... \ prjdemo directory (local project) use the import command or tortoisesvn to import the prjdemo/trunk directory of SVN server, such as SVN: // hostip/prjdemo/trunk

8. Check out a local copy. The normal SVN operation cycle starts.
Update local copy
Alter modify local content (working properly)
Update-> resolve confict
Commit
... Create tags for a specific version (in fact, a specific version is admitted to the tags directory), branch operations

Note that the version number of the Subversion is for the entire version library, not for files.

Now, the basic version is ready for use. For details about how to back up a version database, seeArticleSVN administrator configuration, details