On Sat, Feb 12, 2011 at 2:25 PM, David Chapman <dcchap...@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
