Configuring the svnserve daemon

Creating the repositories If you have not created any subversion repositories yet, you can create one with svnadmin: # svnadmin create ~/my-repository Tweaking svnserve.conf Open up and edit the svnserve.conf file located in the $HOME/my-repo/conf/ directory. Sample $HOME/my-repo/conf/svnserve.conf [general] # Path to the file containing svn users and passwords. password-db = $HOME/my-repo/conf/passwd # Authentication realm of the repository. Two repositories using the # same password-db should have the same realm. realm = My-test-repository # Deny all anonymous access anon-access = none # Grant authenticated users read and write privileges auth-access = write Setting up password authentication Open up and edit the password-db file (ie. $HOME/my-repo/conf/passwd). A sample entry might look like this: ...

29 March 2009 @ 12:59 · Updated: 30 June 2026 @ 03:28 · leo

Configuring subversion access over HTTP/DAV

Creating the repository If you have not created any Subversion repositories yet, you can create one with svnadmin: # svnadmin create ~/my-repository Adding mod_dav_svn to your httpd # a2enmod mod\_dav\_svn If you plan to use fine-grained permissions, load mod_authz_svn.so as well: # a2enmod mod_authz_svn Configuring access to repositories HTTP access to your repositories is defined using a <Location> section in your httpd.conf. <Location /myproject> DAV svn SVNPath /home/myself/myrepos/myproject AuthType Basic AuthName "My project" AuthUserFile /home/myself/private/myproject.pw Order deny,allow <LimitExcept GET PROPFIND OPTIONS REPORT> Require valid-user </LimitExcept> </Location> This entry would grant read-only access to everyone and write access to every user AuthUserFile. You can use the htpasswd utility to create or update this file, as described here. ...

29 March 2009 @ 12:53 · Updated: 30 June 2026 @ 03:28 · leo