AFAIK, mod_dav_svn requires configuration that is not compatible with
mod_userdir.
My suggestion would be to put the repo in /home/<user>/svnrepo and then have
symlinks to gather them all in a single place, then use SVNParentPath to
serve them, and mod_authz_svn to limit users to their own repo.
its more work, but its somewhat required
On Jan 5, 2008 12:07 PM, Seb <spluque_at_gmail.com> wrote:
> Hi,
>
> I'm trying to set up a repository for a user in a Debian unstable
> system. Apache 2.2.6 already serves users' public directories, with the
> following in /etc/apache2/mods-enabled/userdir.conf:
>
> ---<---------------cut here---------------start-------------->---
> <IfModule mod_userdir.c>
> UserDir disabled root
> UserDir "WWW"
>
> <Directory "/home/*/WWW">
> AllowOverride FileInfo AuthConfig Limit
> Options MultiViews Indexes SymLinksIfOwnerMatch
> IncludesNoExec
> </Directory>
> </IfModule>
> ---<---------------cut here---------------end---------------->---
>
> The server also has the dav and dav_svn modules loaded. I would like to
> make the repository inaccessible for anything other than subversion
> clients. Does this sound like a reasonable thing to do, any gotchas?
> Or would it be better to put the repository under another directory (but
> inside the user's directory), and create a virtual host for it? Any
> suggestions welcome.
>
>
> Cheers,
>
> --
> Seb
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
> For additional commands, e-mail: users-help_at_subversion.tigris.org
>
>
Received on 2008-01-05 20:32:04 CET