Re: Creating a repository

Jody Shumaker wrote:
> We went with a repository structure that holds multiple projects. With
> your setup though, sounds like you may also want to be changing the
> access permissions on a fairly constant basis, which also isn't some
> quick thing that can be done through a gui. Our setup though, any
> developer could go in and create a new directory for a project in the
> current repository. I can see reasons though not to adopt this approach.
> We're also a smaller company and technically I'm not the IT guy, but
> just the guy who promoted SVN and got it all setup.
>
> You might just want to consider if you could keep one repository for all
> your projects. Otherwise, Stefan's idea of using a remote share to some
> trusted users sounds like a great solution.

You only have to restrict the access to the *share*. The server (apache)
has of course full access to those repositories, and the users accessing
the repository via https:// are authenticated against our windows domain
controller with mod_auth_sspi, and all users of the group "Developer"
have access there.

So it's really easy to handle this kind of setup.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org