Shulou(Shulou.com)06/02 Report--

Construction and use of svn

What is svn?

Svn is a cross-platform open source version control system, svn version management tools manage a variety of data over time, this data is placed in a central archive, this archive is very much like a normal file server or FTP server, but, unlike other servers, svn will back up and record every change and update of each file. In this way, we can restore the file at any point in time to an old version we want, or we can directly browse the update history of the specified file.

Disadvantages of svn:

As mentioned above, a copy is retained for each commit, so the database capacity of svn will soar.

If the svn server goes down, it is basically not working

Not suitable for open source system development

Advantages of svn:

Convenient management, clear logic, in line with the thinking habits of ordinary people

Easy to manage, centralized svn server can ensure the security of data.

Version consistency will be more guaranteed.

Suitable for the development of projects with a small number of developers

The popularity is relatively high.

The svn workflow can be divided into the following four steps:

Create or copy a branch from the trunk on a central library

The code for this branch from the central library check out

Add your own code file, modify existing code, or delete code file

Commit code, if someone submitted the code on the branch just now, you will be prompted that the code will expire. You have to up your code first and then submit it. If there is a conflict in up code, you need to resolve the conflict before submitting.

Experiment

Environment building

[root@svnserver] # yum-y install subversion # first of all, download the software

[root@svnserver ~] # mkdir-p / svn/data # create a version inventory directory

[root@svnserver ~] # mkdir-p / svn/auth # create a directory for storing certification-related files

[root@svnserver ~] # svnserve-d-r / svn/data/ # start svn,-d to specify background operation, and-r option to specify version inventory directory

Svnserve available options:

-d [--daemon]: background mode

-I [--inetd]: inetd mode

-t [--tunnel]: tunnel mode

-X [--listen-once]: monitor once (for debugging)

-r [--root] ARG: the root directory of the service

-R [--read-only]: force read-only; overwrite version library configuration file

-- config-file ARG: read the configuration from the file ARG

-- listen-port ARG: listening port

[method: daemon, listen-once]

-- listen-host ARG: listens to the host name or IP address

[method: daemon, listen-once]

-T [--threads]: use threads instead of processes [method: daemon]

-- foreground: run in the foreground (for debugging)

[method: daemon]

-- log-file ARG: svnserve log file

-- pid-file ARG: write process PID to file ARG

[method: daemon, listen-once]

-- tunnel-user ARG: tunnel user name (default is the user name corresponding to the current UID)

[method: tunnel]

-h [--help]: show this help

-- version: displays program version information

[root@svnserver ~] # ps-ef | grep svn | grep-v grep # View svn process

Root 2720 1 0 04:41? 00:00:00 svnserve-d-r / svn/data/

[root@svnserver ~] # lsof-isvn 3690 # View the listening port of svn

COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME

Svnserve 2720 root 3U IPv4 21398 0t0 TCP *: svn (LISTEN)

[root@svnserver ~] # svnadmin create / svn/data/dir # create a version library

[root@svnserver ~] # tree / svn/data/dir/ # after initializing the version library, many files and directories are generated under the version library directory. More important are the conf directory and the hooks directory, the former is used to store and configure related files, and the latter is used to store hook scripts.

/ svn/data/dir/

├── conf

│ ├── authz

│ ├── passwd

│ └── svnserve.conf

├── hooks

│ ├── post-commit.tmpl

│ ├── post-lock.tmpl

│ ├── post-revprop-change.tmpl

│ ├── post-unlock.tmpl

│ ├── pre-commit.tmpl

│ ├── pre-lock.tmpl

│ ├── pre-revprop-change.tmpl

│ ├── pre-unlock.tmpl

│ └── start-commit.tmpl

[root@svnserver conf] # cp svnserve.conf svnserve.conf.bak # get into the habit of saving a backup before modifying the configuration file

[root@svnserver conf] # cat svnserve.conf | egrep-v "(# | ^ $)" # is modified as follows

[general]

Anon-access = read # permissions for anonymous connections

Auth-access = write # authenticate the permissions of the connection

Password-db = / svn/auth/passwd # user authentication file

Authz-db = / svn/auth/authz # user rights file

[root@svnserver conf] # cp authz passwd / svn/auth/ # copy authentication and permission files to a custom directory

[root@svnserver conf] # cd / svn/auth/

[root@svnserver auth] # chmod 700 * # modify permission to 700

[root@svnserver auth] # cat passwd | egrep-v "(# | ^ $)" # modified as follows

[users]

Lhx = 1

[root@svnserver auth] # cat authz | egrep-v "(# | ^ $)" # modified as follows

[dir:/]

Lhx = rw

Restart svn

[root@svnserver auth] # pkill svnserve

[root@svnserver auth] # svnserve-d-r / svn/data/

The use of svn under windows

Create a directory in the windows client, then right-click the directory, select "SVN Checkout", and enter the path to svn's warehouse

Enter your user name and password and click OK

There will be a green tick after success.

Create a file in the svndata directory, then right-click the directory, select "SVN commit", and select the file to upload

Uploaded successfully

View uploaded files on the svn server

[root@svnserver] # svn list svn://192.168.83.134/dir-verbose-username=lhx-password=1

1 lhx May 22 04:59. /

1 lhx 0 May 22 04:59 test.txt

The use of svn under linux

Common command: svn [options] [args]

Checkout (co) # fetches a copy of the working version from the source code library

Commit (ci) # commits changes to the current working copy, where code conflicts may occur

Copy (cp) # make a copy of a working copy

Delete (del,remove,rm) # Delete files or directories locally or on svn server response

Diff (di) # compare the difference between a file and the corresponding file in the library

Export # exports a copy of the directory tree without version control, which is generally used for export release or a running version

Import # imports files from the local current directory into svn response

Info # Information of a file in the working copy of the current directory

Status (stat,st) # svn working copy current status, the result of comparison with the source code on svn server

Update (up) # synchronize svn server-side files locally

[root@client ~] # yum-y install subversion

[root@client ~] # svn co svn://192.168.83.134/dir / svndata-- username=lhx-- password=1 # download the checkout file from the library

A / svndata/test.txt

Checked out revision 1.

[root@client ~] # tree / svndata/

/ svndata/

└── test.txt

If you report an error in checkout:

Svn:Can't convert string from 'UTF-8' to native encoding:

It can be solved in the following ways:

[root@client ~] # export LC_CTYPE= "en_US.UTF-8"

[root@client ~] # export LC_ALL=

Of course, there are many commands and options that will be used in the work, so I won't go into them one by one here. All the above orders are explained, so you can try it by yourself.

If there are any mistakes, please correct them.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.