Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

How to install and use version control system Subversion on CentOS system

2025-01-21 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Servers >

Share

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

This article mainly introduces "how to install and use version control system Subversion in CentOS system". In daily operation, I believe many people have doubts about how to install and use version control system Subversion in CentOS system. Xiaobian consulted all kinds of materials and sorted out simple and easy-to-use methods of operation. I hope it will be helpful to answer the doubt of "how to install and use version control system Subversion in CentOS system". Next, please follow the editor to study!

1. Install Subversion

Yum install subversion

two。 Create a version library

A.mkdir-p / var/svn/repositories (create version library directory)

B.cd / var/svn/repositories

C.svnadmin create rock-eng (create version library rock-eng)

3. Start svn

Svnserve-d-r / var/svn/repositories

4. Configure acc

A.cd / var/svn/repositories/rock-eng/conf/

B.vim 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 = 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

Previous page 123 the next page consists of 3 pages

[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

Vim 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

Rockeng = 123456

Previous page 123 the next page consists of 3 pages

Vim authz

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

E

[groups]

# harry_and_sally = harry,sally

# harry_sally_and_joe = harry,sally,&joe

[/]

# harry = rw

# & joe = r

# * =

Rockeng = rw

# [repository:/baz/fuz]

# @ harry_and_sally = rw

# * = r

5. Restart svn

Killall svnserve

Svnserve-d-r / var/svn/repositories

6. Check out: svn co svn://127.0.0.1/rock-eng

7. Add files: svn add directory

8. Submit changes: svn commit

9. Delete the file but save the local copy: svn delete-- keep-local directory

10. Ignore the data and attachment directories under the current directory

A.svn propedit svn:ignore .

b. Enter the directory name in the editor, separated by carriage return

C.svn commit

11. View the status of the current directory: svn status

Question 1:

Svn: log information cannot be obtained using an external editor; consider setting the environment variable $SVN_EDITOR, or using the-- message (- m) or-- file (- F) options

Svn: no SVN_EDITOR,VISUAL or EDITOR environment variables are set, and there is no "editor-cmd" option in the runtime configuration parameters

Solution:

A.vim / .bash_profile

b. Added: export SVN_EDITOR=vim

At this point, the study on "how to install and use the version control system Subversion in the CentOS system" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

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.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Servers

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report