[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: mod_dav_svn + automatic per-directory user authorization

From: David Brodbeck <brodbd_at_uw.edu>
Date: Tue, 15 Feb 2011 15:37:02 -0800

On Sat, Feb 12, 2011 at 2:25 PM, David Chapman <dcchapman_at_acm.org> wrote:

> Repositories are meant to preserve data, implying they are relatively
> long-lived. Are you suggesting that repositories will be deleted all the
> time? If so, a master server-based configuration like httpd may not be
> appropriate for you at all. You may need something more dynamic like
> svnserve via inetd (look for that subject heading in the Subversion book).
> I don't have any experience with that, however.
> Your access requirements (many small repositories, many users, fine-grained
> path-based authorization) don't sound like what Subversion is designed for.
> It may not be an appropriate tool for you.

This might be exactly what's needed if you're, say, teaching a programming
class where you want students to learn to use Subversion for version control
of their projects. You don't want students to be able to mess with each
others' code, and you probably don't want to retain their data forever once
the class is over.

I don't know if that's the original poster's situation, but that's what it
immediately reminded me of.

David Brodbeck
System Administrator, Linguistics
University of Washington
Received on 2011-02-16 00:37:44 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.