Re: What's the best way to setup repository for multiple clients

[Quinn Taylor]

It really depends on what you mean by "clients". Is each client a single user (like "client-server") or a group of people (like a business client)? I'm assuming the latter, since in the former case it's a matter of creating a login for each user.

HTH,
  - Quinn

On Jun 7, 2009, at 5:31 PM, Chris Sanders wrote:

Subversion does support path-based authentication, such that specific users and groups can only access specific paths, but using it extensively is discouraged. The reason is that users get confused about which parts they can and can't access. It also becomes a maintenance headache for the repository admin. It's generally much cleaner to create a separate repository for distinct groups. If users need to work in multiple repositories, their login information can be the same for each.

I'm trying to figure out what's the best way to setup a repository for
multiple clients?
1) Should I just create one repository for every client
2) Should I make one repository and put all the clients into that?

Because I'd like to set it up in a way that when I need to allow an
external developers on a project, i can control which accounts they
work, there by not giving access to everyone elses accounts.

Thanks
Chris Sanders

smime.p7s
Description: S/MIME cryptographic signature