On Wed, Nov 13, 2002 at 06:09:46PM -0600, Ben Collins-Sussman wrote:
> Josef Wolf <jw@raven.inka.de> writes:
>
> > With this CGI you can do most of the day-to-day administration without
> > logging in to the server. Here are some key features of it:
>
> Cool!
:)
> > - It needs to "apachectl graceful" after repos-creation.
> Why? Isn't SVNParentPath sufficient to prevent restarting apache?
I think SVNParentPath _should_ be enough. But currently (well, at
least in 2.0.43) Apache AuthGroupFile directive seems to be broken, so
this directive is entirely ignored in .htaccess files (I have asked
for this very problem on this list about one or two week ago). But I
needed to get some presentations fast, so I could not wait until
AuthGroupFile would be fixed. Therefore I went the way that the CGI
would write an entire <Location>-Block for every repository in a
specific directory which would be included from the main
httpd.conf. It's a kludge, but I had no time to wait for the fix to
get it right.
At current time I am not sure whether I should wait for the
AuthGroupFile-issue to be fixed or whether I should go ahead and
try the mod_perl way to do proper authentication. I think mod_perl
would be the better choice in the long run...
> > - Would such a script have a chance to find its way into the tools/cgi
> > directory?
> I don't see why not, it sounds like a really useful 3rd-party tool.
Well, if no one shouts "stop", I will do some cleanups on the code,
put some comments into it and post it on this (or next) weekend.
> > - should I share this script _now_ (with the issues mentioned above)
> > or should I fix all the sanity/security issues before I post it?
> Share! The best way to shake out bugs is to hand something that
> "mostly" works to a group of eager hackers. :-)
Well, I am not really concerned on the bugs. But I am somewhat
concerned whether I should post a script which is known to have
security issues.
--
-- Josef Wolf -- jw@raven.inka.de --
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Nov 14 02:19:20 2002