On Nov 5, 2010, at 14:11, Eramo, Mark wrote: > Ryan Schmidt wrote: > >> On Nov 5, 2010, at 13:50, Eramo, Mark wrote: >> >>> I have had success setting up several repositories in Apache as follows... >>> >>> In the httpd-subversion.conf file, I have the various repositories defined >>> like this..... >>> >>> <Location /svn/repo1> >>> SVNPath /path/to/repo1 >>> . >>> . >>> . >>> </Location> >>> >>> <Location /svn/repo2> >>> SVNPath /path/to/repo2 >>> . >>> . >>> . >>> </Location> >>> >>> <Location /svn/repo3> >>> SVNPath /path/to/repo3 >>> . >>> . >>> . >>> </Location> >>> >>> Then when I hit http://server/svn/repo1, I get access to repo1, I hit >>> http://server/svn/repo1, I get access to repo2, etc. >> >> That's exactly what SVNParentPath is supposed to let you do more easily and >> concisely. >> >> >>> As far as a web page goes, you could create a custom index.html that has >>> all the links to the various repositories so if users just goes right to >>> http://server, they see the custom index.html which has all the repository >>> links. >>> There should already be a default index.html in the Apache /htdocs folder >>> that has "It Works!" in it. You could just back that one up and replace it >>> with a new index.html that has the links to all the repositories. >> >> That's exactly what SVNListParentPath is for. >> >> >>> If you use SVNParentPath instead of SVNPath, you can have issues so this >>> seems to work well for me. >> >> What issues are you referring to? > > I had issues with SVNParentPath but I think it was how I set it up. When I > set it up the way I showed, it worked well. When I was doing this, I did not > find docs that explained SVNParentPath well enough to me so maybe that is why > I had the setup issues.
For what you showed, it should simply be: <Location /svn/> SVNPath /path/to/ SVNListParentPath On </Location> That's it.
