Re: Apache: Hidden / Read-Only / Commit

On 5/24/07, Pieter <pietercoucke@hotmail.com> wrote:
> Hi,
>
> I'm planning to install Subversion with Apache, to have all the source code
> of the company in 1 big repository.
>
> Can I (via the Apache Server of Subversion) restrict access to given
> projects in the repository?
> I would like to be able to define for each project seperately in my
> repository:
> - who can see the project and who not (whether or not they can it or browse
> it)

Per-directory access controls. Grant those who can see a project read
or write permission, deny everyone else.
http://svnbook.red-bean.com/en/1.2/svn.serverconfig.httpd.html#svn.serverconfig.httpd.authz.perdir

> - who can do commits to it, and who only updates (in case they can see it)

Per-directory access controls. You can allow some people write
permission, and others read-only. (link above)

> - who has to be warned by email that a commit to a given project has been
> done

Post-commit hook script.
http://svnbook.red-bean.com/en/1.2/svn.reposadmin.create.html#svn.reposadmin.create.hooks

> It's crucial for me that I can do this project by project 'security'. Is
> this possible? And if yes: how?

You don't *have* to keep everything in one repository. You may find it
easier to apply security for some projects by keeping them in their
own separate repository, but still served by the same Apache instance.
If you need finer-grained access than no access/read/write, look into
svnperms.py.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu May 24 15:15:21 2007