Re: Proposal for svnserve configuration

Greg Hudson wrote:
> Con: * If you have many repositories and want the same configuration
> for all of them, it's more of a pain.

Absolutely. If you have a set of users common to a set of repos, you
don't want to have to have each user's password stored in each repository.

Would it make sense for svnserve to accept apache style passwd and
group files? That would make it easy to synchronize the
authentication and authorizatin configuration between svnserve and
mod_dav_svn.

> Question: Should the default for anon-access be none, instead of read?

IMHO, yes, becuse that makes it harder to make a mistake and not
notice it. If the client gets an authentication prompt when he tries
to connect, he knows (or should know) what the problem is, but it's
possible to accidentally leave anon access without ever noticing it.

> Question: When I (hopefully) add path-based auth support, do people
> think I should just fold it into this file, or should it be a separate
> file so that it can have exactly the same format as the mod_authz_svn
> control file?

Sharing the mod_authz_svn format would make the documentation simpler,
and it would make svn easier to learn (and remember).

/Tobias

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 29 00:32:40 2003