Hi Pieter,
yes you can, but from my past experience, it's a little bit of a
pain. First of all, what type of authentication are you using? With
apache, in your svnaccessfile you can have it set up as follows, there
might be a better way of doing this so if anybody knows, please drop
me a note :)
SVNAccessFile:
[Repo:/Project1/]
@admins=rw
Pieter=rw
*=
[Repo:/Project2/]
Pieter=rw
@admins=r
*=
..... well, you get the point. For each project you have to set up
security settings. Hope it helps. Now, I don't have my stuff set up
like that. I have a bunch of repositories with each of them with a
seperate permissions, but from what I've tried before this should
work. Play around with it a little bit and let me know how it turns
out.
Regards,
Ahmed
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)
> - who can do commits to it, and who only updates (in case they can see it)
> - who has to be warned by email that a commit to a given project has been
> done
>
> It's crucial for me that I can do this project by project 'security'. Is
> this possible? And if yes: how?
>
>
> Thanks a lot in advance,
>
>
> Pieter
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
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:20:08 2007