| 41 | Securing a Repository |
Most organizations should use a single Subversion repository for all their projects. You should consider using multiple repositories only if you have run into a roadblock using a single repository, such as needing to support hundreds of users and not having enough room on a single server. Given that a typical Subversion repository supports multiple projects, you’ll often want to limit access to each project to certain groups of users. If you’re hosting your Subversion repository using Apache or svnserve, Subversion’s path-based security can solve the problem.
Path-based security is enabled in Apache by including the AuthzSVNAccessFile directive for your repository. If you’re using svnserve, you need to edit svnserve.conf ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access