>> Thanks. But now there is an other problem:
>> [ ... ]
>> Now I create a repository with "svnadmin create
>> /local/svn/repos/project"
>> and put the following into /local/svn/repos/project/.htaccess :
> AFAIK, the URLs handled by mod_dav_svn are not mapped to
> physical filesystem locations
> under /local/svn/repos, so apache won't look there for an .htaccess.
:-(
> (Moreover I have the impression that you're mixing two
> repository in the same filesystem tree here)
I am trying to hack an cgi-based repository administration tool, so
people can create and manage their repos without logging in onto
the server. This cgi creates all the files which are needed to
control access to the existing repositories. I don't want to put this
information directly into httpd.conf for two reasons: first, it would
require to restart httpd from withhin the cgi. Second, I dont want to make
httpd.conf writable by the httpd process.
> If you want to control access based on different subprojects
> in your repository, you need to use a hook script.
I know.
> Alternatively you can create separate repositories
> for separate projects.
This is exactly what I am trying to do... The cgi would create and
manage the AuthGroupFile for the repos in question. And I would like
to enable/disable browsing of the whole repos (not specific paths
withhin the repos) based on that information. Is there really no way
to do such a thing?
> Perhaps it's possible to do this entirely via the httpd.conf
> file
I would rather not touch httpd.conf from withhin the cgi...
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Oct 22 17:45:29 2002