Best practice for using subversion in web development

I am going to start using subversion for a bunch of websites.  What is the best way to set this up?

I work on about 20+ client websites right now.  Would my best bet to put all the clients websites in one repository?  If so what is the best way to lay it out?  Most of the sites are small business sites, nothing fancy.

Is there any disadvantages in putting all of the clients websites in one repository?
LVL 5
keithslaterAsked:
Who is Participating?
 
sreindl04Connect With a Mentor Commented:
You can put everything into one repository if you do not have doubts about the size of the repository.

The Apache Foundation has put all projects into one subversion repository. Others use several repositories. In our company we use one repository for all projects except for the projects where the customer does not allow storage of their data/software together with other data.

From performance point of view we do not have any problems until now (with several thousands of commits until now).

From maintenance aspect I do not see a big difference except if you have other tools around (svnmailer, scmbug, ...). In this case you might have more maintenace has you have to maintain these tools for every repository.

Regards
Stephen
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.