Linux System Build SVN service detailed process

Brief introduction:

SVN is the abbreviation for Subversion, is an open source version control system, it is simple to say that SVN is used for many people to jointly develop the same project, the purpose of sharing resources. That is, when it comes to SVN, that is, when many people are working together on a project that requires more than one person to maintain the update, SVN is used to provide such a requirement.

First of all, I want to explain my needs I; At present, the company has two projects; I'm going to store two repositories in the same directory on a single server [resource repository plainly, the directory where you have a project]. Then we're going to start configuring it.

One: Linux server-side configuration

1: First is to install the SVN service

The installation method is simple: The SVN Service installation package is already included in the repositories of many Linux systems

Take CentOS for example:

Just:

[[email protected]/]# Yum install subversion

2: Need to create a new directory to store the SVN repository

[Email protected]/]# Mkdir/source

3: Then need to create a new repository of required resources; [I need two repositories in Pro1 and Pro2]

[Email protected]/]# svnadmin create/source/pro1 [[email protected]/]# svnadmin Create/source/pro2

After executing the command above, you will find several files appearing in the directory under Pro1 Pro2:

[Email protected]/]# LS/SOURCE/PRO1 conf db format hooks Locks README.txt

simply say a few of these file uses

Conf: The configuration file of the repository (can set the user access account, permissions, etc.)

DB: All version-controlled data storage files

Format: is a text file in which only one integer is placed. Represents the version number of the current vault configuration

Hooks: The directory where the hooks script is stored [the use of simple points is, for example, when the development team submits the update, does not require you to manually update the server to complete the update]

Locks: A directory used to locate hard-to-lock data in subversion to track clients accessing the vault

4: Next is the configuration:

First configure the SVN service main profile svnserver.conf profile directory/source/pro1/conf/svnserver.conf

The main configuration items are as follows:

[General]

anon-access = Read # the permissions for anonymous access, which can be read,write,none, default to read

auth-access = Write # Authentication User's permissions, can be Read,write,none, default is write[is read and write]

password-db =/source/pro1/conf/passwd #认证用户的密码文件路径

authz-db =/source/pro1/conf/authz #认证用户的权限文件路径

Realm = svn for Pro1 # Authentication namespace, Subversion is displayed in the authentication prompt

5: Configure user access password:

configuration file /source/pro1/conf/passwd

content Format:

[Users] < user 1> = < password 1> Pro1 = Pro1

My configuration:

[Users] Pro1 = pro12345

6: Configure User access rights:

configuration file /source/pro1/conf/authz

content Format:

[< Repository >:/project/directory] @< user group name > = < permissions > < user name > = < permissions >

my configuration: Only Pro1 users have read and write permissions, other users do not have any permissions

[pro1:/] Pro1 = RW * =

The above configuration files are effective in time and do not need to restart the SVN service

7: Start SVN

Svnserve-d-r/source

-D for Demon-r as root the upper directory for the warehouse is the upper level of the Pro1/source

8: Remember to modify the firewall, SVN service default service port 3690, of course, you can also specify the port--listen-port parameter specified

Two: Windows Client authentication

1: Download TortoiseSVN Client Installation

2: After installation, generally in the desktop right-click menu will appear tortoisesvn-->repo-brose and then will pop up a window to enter the URL, and then access

SVN://SVN Server ip/pro1[warehouse name]

3: Enter the corresponding user name: Pro1 Password: pro12345 can enter, just start empty

4: Then you can upload your source code or other files to the SVN server

This article is from the "Epitaph" blog, make sure to keep this source http://epitaph.blog.51cto.com/8834364/1839290

Linux System Build SVN service detailed process