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

Re: SVN "control" dirs showing up to repo clients

From: Nico Kadel-Garcia <nkadel_at_comcast.net>
Date: 2006-08-04 01:26:37 CEST

Andy Levy wrote:
> On 8/3/06, Jeff Barrett <jbarrett@finaplex.com> wrote:
>> We've got a 1.3.2 fsfs repository that we just put together. It's
>> fronted by an apache 2.2 server with a SVNParentPath. When I look at
>> the top level of the repo, either in browser or commandline, I see
>> these dirs in addition to my branches/trunk/tags dirs:
>> README.txt
>> SVN/
>> conf/
>> dav/
>> db/
>> format
>> hooks/
>> locks/
>> And I can interact with them. We could do something like hide these
>> directories via mod_authz_svn configurations, but that seems strange.
>> Should these directories show up to clients or did we do something
>> wrong? If they are supposed to show to clients, do most people leave
>> them available or hide them?
> Something is wrong with your Apache configuration. If you post your
> <Location> section corresponding to the repository(ies), someone can
> probably work it out pretty quickly.

Also, never put your repositories in the same location as your standard
web-browsing. It just causes trouble.

For example, if your parent URL is for http://hostname/svn/repos/, and your
DocumentRoot is set to /var/www/html, never put your repositories in
/var/www/html/svn/repos/[repositorynames]. Always use a "Location" statement
to make the distinction between the repo location and the normal browser
locations clear.

I don't understand all the details of why, but this issue has been around
for a while, and seems to be why the defaults in the Linux RPM's point the
repo to a separate directory than /var/www/html/.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 4 01:27:48 2006

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

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