What is the correct way to setup a repository.

[Devgineer]

Say I have multiple clients and each client has multiple applications that we are developing for them. Should we create a "Customer Name" repository and then a folder for each application or should each application have it's own repository? I'm new to source control and have searched Google for the correct answer but can't find anything useful.

Thank You,

Joshua

[Beth]

This is really a matter of personal preference.

Do any of the projects share code? If so, how much? Code can't be shared across repositories, though multiple copies can be exported from one repository and imported to all the other repositories. Export/Import takes all the history as well. If it's a large amount of code though, you will end up with a much larger database.

If you have a high number of projects, and make a repository for each one, at a certain point the repository list that appears when you are logging in has the potential to have a small delay. If you are going to get over 50 repositories, then it might be in your best interest to not make a repository for every project.

If each individual project is extremely huge so that you have a high number of nodes in your tree (each file and folder represents a node), then having a lot of projects in a repository might slow up your tree when it is first being pulled up. If every project is huge, then dividing into more repositories can help performance.

So that we get an idea of numbers with this, can you tell me how many customers you will have projects for, how many projects you have, and give me an approximate size of the projects?