Version Control with Subversion - Login

Server ConfigurationNote that if mod_dav was compiled as a shared object (instead of statically linked directlyto the httpd binary), you'll need a similar LoadModule statement for it, too. Be sure that itcomes before the mod_dav_svn line:LoadModule dav_moduleLoadModule dav_svn_modulemodules/mod_dav.somodules/mod_dav_svn.soAt a later location in your configuration file, you now need to tell Apache where you keepyour Subversion repository (or repositories). The Location directive has an XML-likenotation, starting with an opening tag and ending with a closing tag, with various other configurationdirectives in the middle. The purpose of the Location directive is to instructApache to do something special when handling requests that are directed at a given URLor one of its children. In the case of Subversion, you want Apache to simply hand off supportfor URLs that point at versioned resources to the DAV layer. You can instruct Apacheto delegate the handling of all URLs whose path portions (the part of the URL that followsthe server's name and the optional port number) begin with /repos/ to a DAV providerwhose repository is located at /var/svn/repository using the following httpd.confsyntax:DAV svnSVNPath /var/svn/repositoryIf you plan to support multiple Subversion repositories that will reside in the same parentdirectory on your local disk, you can use an alternative directive—SVNParentPath—to indicatethat common parent directory. For example, if you know you will be creating multipleSubversion repositories in a directory /var/svn that would be accessed via URLs such ashttp://my.server.com/svn/repos1, http://my.server.com/svn/repos2, andso on, you could use the httpd.conf configuration syntax in the following example:DAV svn# any "/svn/foo" URL will map to a repository /var/svn/fooSVNParentPath /var/svnUsing the previous syntax, Apache will delegate the handling of all URLs whose path portionsbegin with /svn/ to the Subversion DAV provider, which will then assume that anyitems in the directory specified by the SVNParentPath directive are actually Subversionrepositories. This is a particularly convenient syntax in that, unlike the use of the SVNPathdirective, you don't have to restart Apache to create and network new repositories.Be sure that when you define your new Location, it doesn't overlap with other exportedlocations. For example, if your main DocumentRoot is exported to /www, do not export aSubversion repository in . If a request comes in for the URI /www/repos/foo.c, Apache won't know whether to look for a file repos/foo.c in theDocumentRoot, or whether to delegate mod_dav_svn to return foo.c from the Subversionrepository. The result is often an error from the server of the form 301 Moved Permanently.Server Names and the COPY RequestSubversion makes use of the COPY request type to perform server-side copies of files171