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 SVN version control software in CentOS system

2025-04-10 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 SVN version control software in CentOS system". In daily operation, I believe many people have doubts about how to install SVN version control software in CentOS system. Xiaobian consulted all kinds of materials and sorted out simple and easy-to-use operation methods. I hope it will be helpful to answer the doubts of "how to install SVN version control software in CentOS system". Next, please follow the editor to study!

Run the svn command on the terminal. If there is no installation, you will be prompted to install

1. First, you need to install the Subversion software:

The code is as follows:

Sudo apt-get install subversion

two。 Create a folder as the root of the version library

The code is as follows:

Mkdir / var/svnroot/

This directory itself is not a version library, but a directory used to install the version library.

3. Go to this directory and create a version library

The code is as follows:

Cd / var/svnroot/

Svnadmin create vlink

If you have multiple projects in the future, you can continue to create the new version library under / var/svnroot/

4. Configure vlink cd / var/svnroot/vlink/conf/ ls

You will see the following files:

The code is as follows:

Authz passwd svnserve.conf

Edit svnserve.conf first

The code is as follows:

Vim svnserve.conf

Where anon-access represents the permissions of anonymous users, and auth-access represents the permissions of authenticated users. Remove the previous # comment and write at the top. Generally speaking, it will be fine like this:

The code is as follows:

Anon-access = none

Auth-access = write

Then you can see that there is a password-db configuration item below. This is the password file used by the configuration.

The code is as follows:

Password-db = passwd

In order to run multiple versions of the library at the same time in the future, it is recommended to change this file to / var/svnroot/. For example: / var/svnroot/passed

The code is as follows:

Password-db = / var/svnroot/passed

In the same way, the same goes for authz-db, like this:

The code is as follows:

/ var/svnroot/authz

Then there is something called realm, which seems to be a prompt sentence when connecting to a svn server. But it must be the right name to set to vlink. Like vlink.

The code is as follows:

Realm = vlink

Don't care about the rest. Save exit.

6. Edit / var/svnroot/passwd

This is simple, just like this:

The code is as follows:

[users]

Username=password

Username=password

7. Start svnserve

The code is as follows:

Sudo svnserve-d-r / var/svnroot/

The parameter after-r is the svnroot location, not the location of a version library

To shut down svnserve, you can end that process directly with kill.

8.Configure iptables

If iptables is set on the server, you need to open port 3690.

The code is as follows:

Iptables-An INPUT-p tcp-I eth0-- dport 3690-j ACCEPT

/ sbin/iptables-An INPUT-p tcp-I eth0-- dport 3690-j ACCEPT

Check ipatbles: iptables-L if the following line indicates that the setting is successful: … ACCEPT tcp-anywhere anywhere tcp dpt:svn

9. The test is local

The code is as follows:

Svn co svn://xxx.xxx.xxx.xxx/vlink-username xxx-password xxx

If you still have any questions, I suggest commenting out the relevant authz in the svnserve.conf file and testing it.

I had the above problems when I did it. Later, I just got better after my brother commented it out. I don't understand the specific reason.

How to backup, export and import the files in the desired svn library (I haven't tested it here, you can test it, let's discuss it together)

10. Export the original Repository as a file dumpfile

The code is as follows:

Svnadmin dump path/to/old-repo > dumpfile.svn

Import dumpfile into the new Repository

The code is as follows:

Svnadmin load path/to/new-repo < dumpfile.svn

11. The fast migration method of native svn:

The code is as follows:

Svnadmin hotcopy old_rep_path new_rep_path

twelve。 Copy the configuration file of the original server to the new server after backup

The code is as follows:

/ etc/httpd/conf.d/subversion.conf

In addition, authfile and auth.conf under the repository directory also need to be backed up and copied to the new server.

The method of relocating SVN URL under 13.linux:

If you replace the SVN server, you need to relocate to point to the new SVN URL.

Reposition command:

The code is as follows:

Svn switch-relocate

Original svn address new svn address

How do I view the original svn address?

View the original svn path method:

The code is as follows:

Svn info

At this point, the study on "how to install SVN version control software 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