You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Brian Osmus <os...@yahoo.com> on 2008/12/03 19:15:51 UTC
Access Control
We have one or more directories we need to be able to control “read”
access to, and since branches can be created, the directory can move around,
and we need to minimize maintenance of having to continuously add restrictions
to where those “read restricted” directories live. This has led to a cluttered and complex access file. Is there way to control the read access with hooks or something else.
Thanks, Brian
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=979036
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: Access Control
Posted by David Weintraub <qa...@gmail.com>.
You can't control "read" access with hooks. There is no pre-checkout hook.
Since there is no hook on checkout or "svn ls", you have to control read
access in the server configuration.
You maybe over thinking the read permission business. Most people only setup
read permission on the entire repository. A few bigger sites set up read
permission on projects. For example, one place where I worked had their
repository layout like this:
http://server/repository/department/project/...
We did access on the department level of our repository. Once you were in a
particular department, you had read access to all projects in that
department. Now, there could be commit restrictions once you get down to a
branch or even file level, but read restrictions were generally more broad
--
David Weintraub
qazwart@gmail.com
On Wed, Dec 3, 2008 at 2:15 PM, Brian Osmus <os...@yahoo.com> wrote:
> We have one or more directories we need to be able to control "read" access
> to, and since branches can be created, the directory can move around, and we
> need to minimize maintenance of having to continuously add restrictions to
> where those "read restricted" directories live. This has led to a cluttered
> and complex access file. Is there way to control the read access with hooks
> or something else.
>
> Thanks, Brian
>
>
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=979275
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].