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

Re: authz access file problem

From: JM Ibanez <jmibanez_at_gmail.com>
Date: 2004-11-10 20:04:12 CET

On Mon, 8 Nov 2004 22:59:59 +0100, Sören Kuklau <chucker@mystfans.com> wrote:

> Unfortunately, this is indeed *exactly* what's happening now. It is
> clear through `svn ls` that the directories /exist/ - they're just
> never checked out unless you explicitly ask svn to, and even then,
> things just don't work correctly at all. I suppose the only true
> solution to this problem* is to use separate repositories.
> *) The problem being: we have a software project with a server (under
> GPL), and several clients, some of which aren't open-source. For
> obvious convenience reasons, though, we'd still like to have the client
> sources in the repository, accessible for developers only. Using authz
> for this seemed like the obvious solution, but I guess not?

Ref: http://svnbook.red-bean.com/svnbook-1.0/ch06s04.html#svn-ch-6-sect-4.4.2
-example 6.3

You might want to note that you *can* offer anonymous access to the
root, and authenticated, r/w access to various trees in the repository
via authz.

You can, for example, deny anonymous access to a particular directory tree:


- which removes any access to anonymous users for that tree. So, you
could use something like this:




- which will give all developers r/w access to the whole repository,
while giving anonymous users r/o access only to the root, and not to


JM Ibanez
   - A million monkeys can't go wrong...
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 10 20:04:51 2004

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.