> -----Original Message----- > From: Ryan Blue [mailto:rdb...@gmail.com] > Sent: 09 August 2011 18:00 > To: users@subversion.apache.org > Subject: mod_dav_svn configuration > > Hello, > > I'm trying to use mod_dav_svn to host repositories that are > arranged in project directories and I can't get the configuration > to work. My projects look like this: > > /srv/svn/project1/repo1 > /srv/svn/project1/repo2 > /srv/svn/project2/repo1 > > I'm running into trouble configuring mod_dav_svn; all I can > find in the documentation is to use SVNParentPath, but the path > given must be the direct parent of SVN repositories. I would > have to supply /srv/svn/project1 and /srv/svn/project2 in > separate Location directives to apache. The problem that I'm > running into is that these project directories are dynamically > created and I need a way to configure all potential project > directories without creating a separate Location directive for > each and restarting apache.
Whilst I agree with a general need for SVNParentPath to be able to cope with trees rather than a single level, I was wondering why you need this? Could you not just have the <project-n> parts as repositories and build the <repo-n> structure inside the repositories? Also, do you (not) have different access requirements that apache applies differently for each <Location>? <snip> > I'm also open to the idea of contributing a patch for mod_dav_svn > to do this, if that is what is necessary. It seems like a good > solution would be to add a SVNSearchParentPath option that causes > mod_dav_svn to check each directory in the path until it finds a > valid repository, i.e., contains a 'format' file with a valid > format code. ...yes please! I would appreciate that too... ~ mark c
