# firewall-cmd -add-service=http -permanent Since you will be accessing SVN via a web interface, you will need to allow HTTP (and optionally HTTPS) traffic through your firewall. Step 3 – Add Security and Create SVN Repository # chgrp www-data /etc/apache2/subversion-auth
# chgrp apache /etc/httpd/subversion-auth # htpasswd -cB /etc/apache2/subversion-auth tecmintĭon’t forget to set the right ownership and permissions to the authentication file: - On CentOS / RHEL / Fedora. # htpasswd -cB /etc/httpd/subversion-auth tecmint Note that by today’s standards, the default MD5 or SHA encryption used by htpasswd are considered insecure. For the first user only, we will need the -c option.Īllowed accounts and bcrypt-encrypted passwords ( -B) will be stored in /etc/httpd/subversion-auth in key-value pairs. We will now use htpasswd to create a password for accounts that will be allowed to access SVN.
Configure svn install#
On the client side (a Windows 7 machine), we will install and use TortoiseSVN (which is based on Apache Subversion) as an interface to SVN.
For our tests we will use a CentOS 7 server with IP 192.168.0.100. That said, let’s roll up our sleeves and install these tools on a RHEL / CentOS 7, Fedora 22-24, Debian 8/7 and Ubuntu 16.04-15.04 server. With the help of mod_dav_svn (Apache’s module for Subversion), you can access a Subversion repository using HTTP and a web server.
Configure svn software#
In the free software ecosystem, the most-widely used version control system is called Apache Subversion (or SVN for short).
Configure svn update#
If your work requires handling documents, web pages, and other type of files that are regularly updated, you may want to use a version control mechanism if you are not doing so already.Īmong other things, this allows you (and a group of potential collaborators as well) to track changes made to a given file, and lets you roll back to a previous version if an issue is encountered or when an update has not produced the expected result.