On Nov 30, 2005, at 20:12, Clemens A. Mensik wrote:
>> We need to create a dozen or so repositories.
>> We have a directory on the server, say /srv/www/svn/
>> This is configured using this version of the <location> directive:
>> <Location /svn/>
>> SVNParentPath /srv/www/svn/
>> DAV svn
>> We know this allows us to create multiple repositories in
>> this directory but it does not allow us to browse the
>> <hostName>/svn/ either in a browser or using a client (we use
>> TortoiseSVN on windows).
> why doesn't it allow you to browse repositories? I've got the
> same config and it works fine... got one rep for all of our
> customers that looks like
> and it works fine, maybe you should use "SVNPath" instead of
> "SVNParentPath" which I've never used (what is it good for)?
> why not just 'normal' SVNPath, i.e.
> SVNPath D:\repository
The reason it works for you is that you have one repository whose
path is specified with SVNPath. Subversion is designed to show you
things inside the repository. Richard has multiple repositories, the
parent of which is specified with SVNParentPath. The directory
specified with SVNParentPath is not a repository, and Subversion <
1.3.0 is not designed to show you things that aren't in repositories.
Richard should not use SVNPath because he does not want to host one
repository; he wants to host multiple repositories.
You can of course write a (PHP|Perl|CGI|Ruby|Python|...) script to
read the contents of the directory pointed to by SVNParentPath and
output that as an HTML page, and indeed such a script exists (or
existed) somewhere on the TortoiseSVN web site for some reason, but
with Subversion 1.3.0 around the corner it's probably not worth the
> PS: why can't I do a "normal" reply to reply to the
> mailing list? *grrr*
Because the mailing list administrators subscribe to this viewpoint:
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Wed Nov 30 23:09:57 2005