How to use SubVersion

SubVersion is a version control system that has only recently begun to pop up. And the author is the main author of the CVS system. First on the PHP & more Vol.4 to see the introductory article, not how to heart, recently because of the need to try to configure a lightweight server type. Although the Sword walk slant, or take the experience to share with you.
If you have the conditions, you can look at PHP & more Vol.4 on the introduction of the article, after all, said that most of the requirements are combined with Apache application, and the description is much more detailed than me. Or a good friend of English can go to the Help manual to find the most appropriate and direct answer. The whole system is divided into:
SubVersion, downloaded from the http://subversion.tigris.org/, is the software that implements the service system.
TortoiseSVN, download from http://tortoisesvn.tigris.org/, is a very good SVN work program, combined into the file manager, easy to use.
SVNService.exe, downloaded from http://dark.clansoft.dk/~mbn/svnservice/, is a portal program that is designed to be used as a Win32 service hook for SubVersion development.
Install SubVersion, and then use the Svnadmin create work area, such as Svnadmin create d:/subversion/proj1. Try using the File Manager to view the directory of proj1, which is packed with the database structure needed for version control.
Then, as stated in the introduction article, you can create an SVN server instance with D:/subversion as the working root through svnserve-d-R d:/subversion. However, this instance, like Tomcat, must be hung through the command line window.
And then I tried it. Using the sc.exe provided by Microsoft to promote Svnserve.exe to service, it turns out that this is not the way to hang a service. Had to turn back to the honest use of SVNService.exe. The SVNService.exe command to achieve the same effect is svnservice-install-d-R d:/subversion. Finally, change Svnservice to automatic startup in service management.
By this time, a normal use of the lightweight SVN server has been built successfully. With the SVN program you can achieve most of the requirements, if you find it troublesome, using TORTOISESVN to operate under the GUI interface can accomplish the same requirements.
But so far, this SVN server does not have any authority mechanism. Open the d:/subversion/proj1/conf/svnserve.conf file. Remove the pre-line annotation with # starting with the following valid structure:
[General]
Anon-access = None
auth-access = Write
Password-db = PASSWD
Realm = Input your password ^_^
Save Svnserve.conf, then a unauthenticated user does not have access to verify that the user has read and write access to the SVN server is basically molded. The last remaining step is to create a suitable PASSWD password management file in the Conf directory.
This place my own experience is the introduction article said is wrong ... I tried using Htpasswd.exe to create a password table, and the SVN server told me that it didn't know this thing-_-!。 I changed the contents of the PASSWD file to something like:
[Users]
Snakevil = 123
root = 234
Such a structure, you can log on normally.
Oh, that's it, all ready to go. ^_^ The content of the development Project SVN import, and then start.