This is what the SVNParentPath is for. IE, I've done that (used
SVNParentPath). I have one whole subdomain that's JUST for my
repositories. One thing that would be REALLY neat is if parent path
would allow me to view a listing of all the repositories in the system.
(I guess my root of the subdomain could be considered a meta repository.
LOL)
On Wed, 2002-10-16 at 11:16, stephen mccaul wrote:
> So i figured out what is causing this but i would like to understand
> this more. It looks like i assumed something about apache that is not
> so.
>
> httpd.conf:
>
> DocumentRoot "/repository"
> <Location "/mike">
> DAV svn
> SVNPath /repository/mike
> </Location>
>
>
> Notice that my repository is in the document root. I thought this was
> cool since directory indexing would give me the list the repsoitories
> and i could browse them all without any effort on my part to create an
> index. This part worked fine.
>
> Unfortunatly because of this when svn does 'PROPFIND /mike' apache says
> '301'. Is apache looking in '/repository/mike' before using the
> information in the <Location> block? Can i adjust these priorities?
>
> when i move the document root elsewhere there are no problems accessing
> the repository. I would still like to get my free indexing but this is
> of course an easily avoidable problem.
>
>
> It seems like it might be good to recommend that people not put
> repositories in their document root.
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
--
Jeff Stuart <jstuart@computer-city.net>
Received on Thu Oct 17 16:58:09 2002