<div>
<div class="content wysiwyg-content">
I am going to start using subversion for a bunch of websites. &nbsp;What is the best way to set this up?<br />
<br />
I work on about 20+ client websites right now. &nbsp;Would my best bet to put all the clients websites in one repository? &nbsp;If so what is the best way to lay it out? &nbsp;Most of the sites are small business sites, nothing fancy.<br />
<br />
Is there any disadvantages in putting all of the clients websites in one repository?
</div>
</div>


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?

Best practice for using subversion in web development

Version control, also known as revision control or source control, is the management of changes to documents, computer programs, large web sites, and other collections of information. Changes are usually identified by a number or letter code, termed the "revision number," "revision level," or simply "revision." Version control systems (VCS) most commonly run as stand-alone applications, but revision control is also embedded in various types of software such as word processors and spreadsheets, and in various content management systems. Revision control allows for the ability to revert a document to a previous revision. Git, a widely-used VCS, has its own topic; other popular systems include CVS, Subversion, Team Foundation Server (TFS), Visual SourceSafe (VSS) and Perforce.