an svn description <?xml:namespace prefix = o ns = "Urn:schemas-microsoft-com:office:office"/>
Subversion is built on Apr. The APR full name Apache Portable Runtime Library is an independent and portable library that any application can use (Apache is also developed based on APR). This allows subversion to work on any operating system that can execute Apache, such as Windows, Linux, various BSD, MacOS, NetWare, and so on.
Subversion has two modes of operation, one that can be used as a module of Apache 2.0 to communicate with the outside world with the Webdav/deltav protocol, and a small server program with subversion itself. The program uses a self-contained communication protocol that can be easily used via SSH in a tunnel manner.
The simplest way to install subversion is to use the binary version that it provides (on the project site, there are files downloaded in the form of RPM, Deb, and Ports).
The way to access SVN is HTTP, HTTPS, SVN, svn+ssh, and so on, we use the https+ certificate.
Two SVN server configuration (RedHat EL 4 system)
Related documents:
RPM Package: Apr-<?xml:namespace prefix = st1 ns = "Urn:schemas-microsoft-com:office:smarttags"/>0.9.4-24.5.i386.rpm, apr-util-0.9.4-21.i386.rpm, neon-0.24.7-4.i386.rpm, perl-uri-1.30-4.noarch.rpm, subversion-1.4.6-0.1.el4.rf.i386.rpm, mod_dav_svn-1.4.6-0.1.el4.rf.i386.rpm;
Certificate tools: Ssl.ca.tar//https Access certificate making Tools
Configuration file: ssl.conf//ssl Access profile
SUBVERSION.CONF//SVN Authentication Authorization configuration file.
(Ready to install the SMB service and copy the above files to the shared directory)
1 Install Redhat el Operating system to SVN library machine (SVNIP), after successful installation, view httpd, Apr, Apr-util, neon, Perl-uri package is installed,
Way:
#rpm-Q httpd
#rpm –q Apr
#rpm –q Apr-util
#rpm –q Neon
#rpm –q Perl-uri
If it is not installed, you will need to download the appropriate RPM package installation before performing the following actions.
and confirm that http://svnip/or https://svnip can be accessed, that is, the Web service is running normally;
Start httpd service httpd start, try to open the connection
。。。 Be sure to ensure that https://localhost can access the following steps
2 Installing SVN software
2.1 Installation Subversion, MOD_DAV_SVN package;
After you have entered the SMB common items directory that you previously set up, do the following
Command # RPM–IVH subversion-1.4.6-0.1.el4.rf.i386.rpm,
# RPM–IVH mod_dav_svn-1.4.6-0.1.el4.rf.i386.rpm;
2.2 Make a backup of the ssl.conf and subversion.conf files in the/etc/httpd/conf.d/directory, and then copy the files ssl.conf and subversion.conf to the directory/etc/httpd/conf.d/. The subversion.conf file is the configuration of the SVN library's basic access (which is configured according to the specific authentication option).
After you have entered the SMB common items directory that you previously set up, do the following
CP ssl.conf/etc/httpd/conf.d/
CP subversion.conf/etc/httpd/conf.d/
3 Establishment of directory/repository
#mkdir/repository
#chmod 777/repository
3.1 Build SVN library,
# Cd/usr/bin
(Svnadmin directory/usr/bin/svnadmin)
#./svnadmin Create/repository/test,test is the name of the specific project library, preferably any name, such as Project1.
3.2 Creating an Authorization directory Repository/auth
#cd/repository/
#mkdir Auth
#chmod 777 Auth
Establish an authorized user file # htpasswd-c/repository/auth/authfile Administrator Hello
(Note: Username Administrator password Hello)
#cd/repository/auth/
# htpasswd–b Authfile User Pass//Add Users
# htpasswd–d Authfile User//delete users
Establish the Permissions profile/repository/auth/auth.conf for authorized users to access the SVN library, in the following format:
(to establish a group or user rights, you need to write below, the middle do not play the space bar, otherwise will cause users or groups are not available)
[Groups]//user group definition
harry_and_sally = TEST,TEST2//indicates that the Harry_and_sally group has member test, test2
[test:/]//test Warehouse root access permissions configuration