[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Separate projects via ra_dav

From: Michael Wood <mwood_at_its.uct.ac.za>
Date: 2003-06-10 11:01:24 CEST

On Tue, Jun 10, 2003 at 05:45:07PM +1000, leif.eriksen@hpa.com.au wrote:
> As each project is a separate repository (that is my proposed layout),
> each repository gets a <Location> entry in the httpd.conf file if I
> envision that projects developers will need web-based access.
> And that is a lot of entries.

Use just one <Location> block, but use SVNParentPath instead of SVNPath.
See Chapter 5 of the book:


        If you plan to support multiple Subversion repositories that
        will reside in the same parent directory on your local disk, you
        can use an alternative directive, the SVNParentPath directive,
        to indicate that common parent directory. For example, if you
        know you will be creating multiple Subversion repositories in a
        directory /usr/local/svn that would be accessed via URLs like
        http://my.server.com/svn/repos2, and so on, you could use the
        httpd.conf configuration syntax in the following example:

        <Location /svn>
          DAV svn
          SVNParentPath /usr/local/svn

        Using the previous syntax, Apache will delegate the handling of
        all URLs whose path portions begin with /svn/ to the Subversion
        DAV provider, which will then assume that any items in the
        directory specified by the SVNParentPath directive are actually
        Subversion repositories. This is a particularly convenient
        syntax in that, unlike the use of the SVNPath directive, you
        don't have to restart Apache in order to create and network new

Michael Wood <mwood@its.uct.ac.za>
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jun 10 11:02:51 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.