one. Install SVN server (operating system CentOS)
Yum Install Subversion
by subversion-v If the command is successfully installed to view
Warm tips do not assume any subversion command to create an SVN library
To run the command:
Mkdir-p/svn/repos
Svnadmin Create/svn/repos
Cd/svn/repos
Ls
Can see a lot more files and directories:: Conf db format hooks Locks README.txt
At this point the installation of Svnserver is basically complete.
two. SVN configuration
Cd/svn/repos/conf
Ls
Able to see files: Authz passwd svnserve.conf
1. First configure the passwd file
VI passwd
Join a similar account
M0SH1 = Admin
#格式为 username = password
Save exit
2. Configuring the Authz File
Join content
[/]
M0sh1
#这两句表明 user M0SH1 access to the entire folder (you can set more specific folder permissions on your own)
3. Configure svnserve.conf
Anon-access = None # Enables unauthorized users to access
auth-access = Write # Enables authorized users to have write permissions
password-db = password # password file
authz-db = authz # access Control file
Realm = M0sh1svn
The default configuration is used. The above statements must be shelf written, the left side can not be blank, otherwise it will be wrong.
three. Turn on the service to test
Start SVN
Svnseve-d-r/svn/repos
#假设已经执行了svn want to create one more. Ability to resolve this issue by setting a different port
svnseve-d-r/svn/repos2--listen-port 3313
After successful launch, we can connect via local TortoiseSVN (TortoiseSVN self-search and download)
SVN link Address:
Svn://server address (assuming port is required to add Port:p ort number)
Four. Create a project
1. You can use the command directly on the server where the SVN server is located
SVN Improt Project Import projects
SVN add file Add files (folder)
2. Under Windows, use the TortoiseSVN tool to select the project folder right click on Import leave a message submission can
3. Under Windows new folder right mouse select checkout. Then copy the project files to this folder, then right-click commit (Leave message)
Five. SVN version number management
The structure of SVN is usually this:
SVN://your project
+trunk/
app/
lib/...
+branches/
+braches_1.0/
+tags
+tag_release_1.0
When there is a need for development. Branching (branch) from the trunk (trunk), when a branch development is complete, the test error should be
Merge onto the trunk, assuming there is a problem on the trunk to make some changes in the trunk. At the end of a phase, there is a stable project that can be published
The version number will be able to make a tag.
The trunk should always be placed in a stable version number, developers in the branch should often synchronize with the trunk (trunk merge to Branch
This does not change the trunk code). Otherwise you'll be getting farther away from the trunk version number. When the branch is merged into the trunk, it will be submitted to commit after careful testing.
(but commit should be as soon as possible to prevent others from changing the trunk too)
Of course the overall process should be set according to the actual situation.
The svn merge can be searched separately for relevant data. ^ _ ^
The following section will briefly summarize the use of SVN hooks.
For example, if the above is a Web project, trunk update, the same time the Web test server also updated trunk code.
Copyright NOTICE: Reprint Please specify source: HTTP://BLOG.CSDN.NET/M0SH1
SVN use (one)
