Another option is to use mod_perl to build the individual blocks for each project using some logic. You could have it grab a list of project dies with ls (if they are in the same parent dir), or use a flat file or SQL database. The drawback is that you have to reload Apache for changes to take effect.
Matt Daniel Shahaf <d...@daniel.shahaf.name> wrote: Ryan Schmidt wrote on Tue, Aug 09, 2011 at 20:07:39 -0500: > On Aug 9, 2011, at 11:59, Ryan Blue wrote: > > > 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. > > [snip] > > You've got it, basically. There isn't a way to configure SVNParentPath > to do what you want, and Subversion doesn't play nicely with Apache > redirects, so I recommend you conform your repository layout to http://subversion.apache.org/docs/release-notes/1.7#http-redirects (the response codes were added to that section three minutes ago)
