使用svn://協定進行版本權限控管

在預設svnserve的模式中不進行權限控管，因此無論進行任何動作皆無限制，並且不會記錄開發人員名稱，若日後發生問題將無從查起。

因此我們必須加入權限控管的設定。

開啟D:\SVN_Repository\repository\conf下的二個檔案。

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.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 = read

# 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 conf directory.

### Uncomment the line below to use the default password file.

# password-db = passwd

### 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

將

[general]

anon-access = read

auth-access = write

password-db = passwd

註解移除

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

修改為

[users]

帳號 = 密碼

即可