Subversion Project Organization: Intro
When organizing the repository structure for maintaining the code base, system admins adopt two basic formats for Project organization in subversion. This depends on the needs of the project and it can be varied over a period of time, depending on the scope defined for the code base. Subversion is very flexible in handling these changes and is easier to maintain than most other products in the market.
Subversion: Folder Organization
SVN: First organization is to allow multiple projects which are loosely tied together.
/var/www/svn
/var/www/svn/repos1
/var/www/svn/repos1/conf/
/var/www/svn/repos1/db/
/var/www/svn/repos1/hooks/
/var/www/svn/repos1/locks/
/var/www/svn/repos1/format
/var/www/svn/repos1/branches
/var/www/svn/repos1/trunk
/var/www/svn/repos1/tags
/var/www/svn/repos2
/var/www/svn/repos2/branches
/var/www/svn/repos2/trunk
/var/www/svn/repos2/tags
SVN: Second organization is to have projects organized which are tied to each other. A change or revision in one project is reflected in the other projects as well.
/var/www/svn
/var/www/svn/branches
/var/www/svn/trunk
/var/www/svn/tags
/var/www/svn/project1
/var/www/svn/project2
These two organization form the basis for the other trees that may grow for managing a project or multitude of projects.
