Svn服务器的安装配置

从http://subversion.apache.org/packages.html上下载svn服务器端

下载下来是这样的东西:

单击Setup-Subversion-1.7.7.msi进行安装svn服务器端

安装完成之后,svn安装的路径的bin会自动加到path环境变量下

如果path环境变量中没有则手工加上

查看是否安装成功，下cmd中运行命令svnserve –-version

注意version前面有2个  -

注意：此时的svn服务器的安装在了D:\Program Files下面

出现上图说明安装成功

配置windows下svn 服务随着windows系统的启动自动启动

注意binpath 变量的值是指定到svn服务器的安装目录下的svnserve.exe,这里的svn安装目录是D:\Program Files下面,

如果安装路径指错，会导致虽然svn服务看起来创建成功，

但是当执行net start SVN-Service命令时，会报出   找不到指定文件 的错误

执行下面的命令

sc create SVN-Service binpath= "D:\Program Files\Subversion\bin\svnserve.exe --service -r D:\software\myeclipsesvn" displayname= "SVN-Service" start= auto depend= TcpIp
binpath 指定svnserve.exe命令的路径
start= auto 表示服务自动启动。注意：等于号的左边无空格，而右边必须有一个空格
Displayname、start、depen
在此命令中-r(--root)项目版本仓库的根目
注意depend= TcpIp 中的Ip中的第一个字母I要大写
如果能看到下图说明成功

查看服务是否添加成功:如果看到下面SVN-Service说明成功

通过命令行启动svn服务:

从windows的服务中看一下

通过命令停止svn服务:

net stop SVN-Service

SVN-Service服务端是否是打开的，还可以通过查看本机的端口号3690是否开启来确认。

每一项服务的开启都有会开启一个独有的端口号如mysql 3306  tomat 8080 等等

可以用netstat -an 命令查看如图

在svn大仓库D:\software\myeclipsesvn下面创建某个项目的仓库BCMark

下面是使用svn客户端的工具创建的

单击确定:

db目录:就是所有版本控制的数据存放文件

hooks目录:放置hook脚本文件的目录。

locks目录:用来放置Subversion文件库锁定数据的目录，用来追踪存取文件库的客户端。

format文件是一个文本文件，里面只放了一个整数，表示当前文件库配置的版本号。

conf目录:是这个仓库的配置文件（仓库的用户访问帐号、权限等）

修改authorz文件

 

### 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:
###  - a single user,
###  - a group of users defined in a special [groups] section,
###  - an alias defined in a special [aliases] section,
###  - all authenticated users, using the '$authenticated' token,
###  - only anonymous users, using the '$anonymous' token,
###  - anyone, using the '*' wildcard.
###
### A match can be inverted by prefixing the rule with '~'. Rules can
### grant read ('r') access, read-write ('rw') access, or no access
### ('').

[aliases]
# joe = /C=XZ/ST=Dessert/L=Snake City/O=Snake Oil, Ltd./OU=Research Institute/CN=Joe Average

[groups]
# harry_and_sally = harry,sally
# harry_sally_and_joe = harry,sally,&joe

# [/foo/bar]
# harry = rw
# &joe = r
# * =

# [repository:/baz/fuz]
# @harry_and_sally = rw
# * = r

[/]
* = rw

passwd

### This file is an example password file for svnserve.
### Its format is similar to that of svnserve.conf. As shown in the
### example below it contains one section labelled [users].
### The name and password for each user follow, one account per line.

[users] 
harry = harryssecret 
sally = sallyssecret

svnserve.conf

### 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.apache.org/ for more information.

[general]
### The anon-access and auth-access options control access to the
### repository for unauthenticated (a.k.a. anonymous) users and
### authenticated users, respectively.
### Valid values are "write", "read", and "none".
### Setting the value to "none" prohibits both reading and writing;
### "read" allows read-only access, and "write" allows complete 
### read/write access to the repository.
### The sample settings below are the defaults and specify that anonymous
### users have read-only access to the repository, while authenticated
### users have read and write access to the repository.
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 a /,
### the file's location is relative to the directory containing
### this configuration file.
### If SASL is enabled (see below), this file will NOT be used.
### 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 the
### directory containing this file.  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 should
### have the same password database, and vice versa.  The default realm
### is repository's uuid.
# realm = My First Repository
### The force-username-case option causes svnserve to case-normalize
### usernames before comparing them against the authorization rules in the
### authz-db file configured above.  Valid values are "upper" (to upper-
### case the usernames), "lower" (to lowercase the usernames), and
### "none" (to compare usernames as-is without case conversion, which
### is the default behavior).
# force-username-case = none

[sasl]
### This option specifies whether you want to use the Cyrus SASL
### library for authentication. Default is false.
### This section will be ignored if svnserve is not built with Cyrus
### SASL support; to check, run 'svnserve --version' and look for a line
### reading 'Cyrus SASL authentication is available.'
# use-sasl = true
### These options specify the desired strength of the security layer
### that you want SASL to provide. 0 means no encryption, 1 means
### integrity-checking only, values larger than 1 are correlated
### to the effective key length for encryption (e.g. 128 means 128-bit
### encryption). The values below are the defaults.
# min-encryption = 0
# max-encryption = 256

添加svn资源库时

一定要启动svn服务器:

提交项目

到此就ok了

 欢迎转载，转载时请注明出处http://www.cnblogs.com/wanggd