Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Why in many examples people try to create separate repository per project?

Why not have single repo and manage access via authz file?

Now it looks for me like extra administrative burden with little benefit...

share|improve this question
up vote 4 down vote accepted

It depends on your organization structure. For many shops a single repository is fine. We used to use a single repository and are now switching over to multiple repositories.

One reason to split it up is because of permissions. If not every is allowed to be in all projects then you can give users access to just the ones they need.

For us it was just a matter of making things a bit easier to deal with from the client side. Once they're set up they're set up. A little extra effort breaking them up to us was worth the ease of use on the client side.

Sometimes people use different repositories for different types of projects, also. Source code in one for the development, product docs in another for the technical writers, etc.

share|improve this answer
Well, you can easily set permissions via authz file per-folder. In this case you manage all the access stuff in 1 file, not in 20 files for 20 different repo's. – BarsMonster Aug 6 '10 at 13:18

We use multiple repositories (one per project) mainly because it is much easier to archive/delete an entire repository. The nature of our business means we do lots of small short term projects for clients that we might not ever hear from again. Being able to move old projects off to tape archive without disturbing any active projects was a major win for us.

share|improve this answer
+1 that's one I forgot about – squillman Aug 6 '10 at 14:24

Having multiple small repository makes it possible to do administrative in a single repository. For example if you have to remove a file from SVN, you basically have to recreate the repository after having passed it through a filter. And this changes the revisions numbers. It is much better to do it on a single project and not affect all other projects.

And if you ask why I should ever remove a file from SVN (that totaly contrary to the essence of source control) : have you ever commited a file with sensitive informations to your repository ? Be it contracts, client informations, database passwords ...

share|improve this answer
Finally, this year SVN would allow us to do this with less hassle :-) Obliteration is coming :-) – BarsMonster Aug 7 '10 at 19:16

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.