You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Mick Ken <mi...@gmail.com> on 2008/06/04 20:52:42 UTC

How to set permission levels in subversion

Hi Friends,
I have a subversion repository and i am controlling the
access/authorization rules using Apache. Right now,

I have a "svn-acl" file that has projects with read-write permissions like:
[ProjectName:/]
@team_project1 = rw

But the problem is, everybody is able to "delete" any folders/files
etc from the repository using the Tortoise SVN repo-browser. So, I
would like to know how to control the permissions so that users cannot
delete anything on the repository and only the Administrator can
delete folders/ files.

I would also like to know how the permission levels should be set like
what's the best way ...

I would really appreciate your input.

Thanks
Mick

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: How to set permission levels in subversion

Posted by Hari Kodungallur <hk...@gmail.com>.
On Wed, Jun 4, 2008 at 1:52 PM, Mick Ken <mi...@gmail.com> wrote:

> Hi Friends,
> I have a subversion repository and i am controlling the
> access/authorization rules using Apache. Right now,
>
> I have a "svn-acl" file that has projects with read-write permissions like:
> [ProjectName:/]
> @team_project1 = rw
>
> But the problem is, everybody is able to "delete" any folders/files
> etc from the repository using the Tortoise SVN repo-browser. So, I
> would like to know how to control the permissions so that users cannot
> delete anything on the repository and only the Administrator can
> delete folders/ files.



The access control has only two levels: read and write. In order to go into
finer grained access control, you will have to write a pre-commit hook.
There is an example script in the source distribution called svnperms.py (in
tools/hook-scripts directory). You might be able to use that in the
pre-commit hook



>
>
> I would also like to know how the permission levels should be set like
> what's the best way ...
>
> I would really appreciate your input.
>
> Thanks
> Mick
>