Download the server program:
Http://subversion.tigris.org/downloads/svn-win32-1.4.3.zip
Download the svn Eclipse plug-in subeclipse:
Http://subclipse.tigris.org/files/documents/906/36425/site-1.2.0.zip
As for tortoisesvn, it is annoying that he hangs folders on his menu, so it is not needed here,
Use the command line and Eclipse plug-in to perform the following operations.
Decompress svn-win32-1.4.3.zip to H:/SVN.
Create the I:/svnroot directory
Run CMD and run:
SC create svnservice binpath = "/" H:/SVN/bin/svnserve.exe/"-- service-r I:/svnroot" displayname = "svnservice" depend = TCPIP
The above command line needs to be executed in one line
Open Computer Management
Find svnservice in service management, set the Startup Type to automatic, and start it.
CMD to H:/SVN/bin
Run svnadmin create I:/svnroot
Install subeclipse
Add the clean parameter to start eclipse
Create SVN connection:
SVN: // 127.0.0.1/
OK
Permission assignment:
Modify the three files under I:/svnroot/Conf
Authz file:
### This file is an example authorization file for svnserve.
### Its format is identical to that of mod_authz_svn authorization
### Files.
### As shown below each section defines authorizations for the path and
### (Optional) repository specified by the section name.
### The authorizations follow. An authorization line can refer to
### Single user, to a group of users defined in a special [groups]
### Section, or to anyone using the '*' wildcard. Each definition can
### Grant read ('R') Access, read-write ('rw ') access, or no access
###('').
[Groups]
Admin = hermit
User = Bob
Test = test
[/]
@ Admin = RW
[/Lms]
@ User = RW
[/Test]
@ User = RW
@ Test = RW
Passwd file:
### This file is an example password file for svnserve.
### Its format is similar to that of svnserve. conf. As shown in
### Example below it contains one section labeled [users].
### The name and password for each user follow, one account per line.
[Users]
Hermit = z
Bob = Bob
Test = tes
Svnserve. conf file:
### This file controls the configuration of the svnserve daemon, if you
### Use it to allow access to this repository. (If you only allow
### Access through http: and/or file: URLs, then this file is
### Irrelevant .)
### Visit http://subversion.tigris.org/for more information.
[General]
### These options control access to the repository for Unauthenticated
### And authenticated users. Valid values are "write", "read ",
### And "NONE". The sample settings below are the defaults.
Anon-access = none
Auth-access = write
### The password-DB option controls the location of the password
### Database file. Unless you specify a path starting with /,
### The file's location is relative to the conf directory.
### Uncomment the line below to use the default password file.
Password-DB = passwd
### The authz-DB option controls the location of the authorization
### Rules for path-Based Access Control. Unless you specify a path
### Starting with A/, the file's location is relative to the conf
### Directory. If you don't specify an authz-DB, no path-Based Access
### Control is done.
### Uncomment the line below to use the default authorization file.
Authz-DB = authz
### This option specifies the authentication realm of the repository.
### If two repositories have the same authentication realm, They shocould
### Have the same password database, and vice versa. The default realm
### Is repository's UUID.
# Realm = my first Repository
After the above Configuration
We can:
The root directory cannot be viewed at will.
Users in the admin group can control all files.
The user in the user group can control all the files in the LMS and test, and cannot see other directories except the LMS, test, and their subdirectories.
The person in the test group can only control all files under test.
If you want to see all the files, you can modify them like this.
[/]
@ Admin = RW
* = R
Start the eclipse connection.
If you want to switch the account, you can change the password on the server side, and eclipse will prompt you to enter the account password again.