Svn is so simple. 1. installation and configuration

Svn is so simple 1 & mdash; installation and configuration 1. Subversion has two running modes: ApacheHttpServer and SubversionStandaloneServer. for details, see linuxsvn installation and configuration, does not work with apache. The following is the installation of httpd-based svn II... svn is so simple. 1. installation and configuration 1. Subversion can run in either of the following ways: Apache Http Server and Subversion Standalone Server. For more information, see linux svn installation and configuration, does not work with apache. Install svn based on httpd 2. install svn [plain] yum install-y httpd-devel subversion mod_dav_svn. You can install the subversion separately. Note that the path must be correct: [plain]. /configure -- with-apxs =/apache path/bin/apxs -- prefix =/usr/local/subversion -- with-apr =/usr/local/apache2 -- with-apr-util =/apache path -- with-ssl -- with-zlib -- enable-maintainer-mode 1 ), confirm that the svn module has been installed: mod_dav_svn [plain] # cd/etc/httpd/modules/# ls | grep svn mod_authz_svn.so mod_dav_svn.so 2 ), check whether svn has been successfully installed [plain] # svn -- version svn, version 1.4.2 (r22196) compiled Aug 10 2009, 18:00:04 Copyright (C) 2000-2006 CollabNet. subversion is open source software, see http://subversion.tigris.org/ This product has des software developed by CollabNet ( http://www.Collab.Net/ ). The following repository access (RA) modules are available: * ra_dav: Module for accessing a repository via WebDAV (DeltaV) protocol. -handles 'http 'scheme-handles 'http' scheme * ra_svn: Module for accessing a repository using the svn network protocol. -handles 'svn 'scheme * ra_local: Module for accessing a repository on local disk. -handles 'file' scheme 3: Create a repository, modify svn configuration file 1), create a repository, [plain] # mkdir-p/var/www/svn # cd/var/www/svn # svnadmin create test # chown-R apache. apache svn 2). edit the svn configuration file [plain] # vi/etc/httpd/conf. d/subversion. conf: [plain] LoadModule dav_svn_module modules/mod_dav_svn.so LoadModule authz_svn_module modules/mod_authz_svn.so DAV svn SVNParentPath/var/www/svn ### Limit write permission to list of valid users .# # Require SSL connection for password protection. # SSLRequireSSL # AuthType Basic AuthName "Subversion repository" AuthzSVNAccessFile/var/www/svn/authz. conf AuthUserFile/var/www/svn/user. passwd Require valid-user # If there is only one warehouse, replace the SVNParentPath parameter with SVNPath, but it is best not to do so. no one is sure that several warehouse will be used in the future, while SVNParentPath can include multiple warehouses, the specified path is the parent directory of all warehouses. 3) add users to create accessible user files [plain] # htpasswd-bc/var/www/svn/user. to add a user to the passwd user name and password, run the following command [plain] # htpasswd-B/var/www/svn/user. passwd username and password 4), permission limit [plain] # vi/var/www/svn/authz. the conf content is as follows: [plain] [test:/] // This indicates, access permissions under the root directory of repository test jason = rw // test repository zhangy users have read and write permissions peterson = r // test repository hunk users have read permissions [/] // this indicates * = r under the root directory of all repositories // This indicates read permission for all users # [groups] // This indicates group setting # svn1-developers = jason, peterson // This represents a member of a group # svn2-developers = jason, kevin # [svn1:/] # @ svn1-developers = rw // If you add the @ symbol above, this indicates that after the group permission settings are completed, restart apache and then access [plain] # service httpd restart. http://your_ip/svn/test Enter the user name and password to go to the svn test database. it is empty and there is no content in it. you can see the new content through this url later.