svn - Should I store all projects in one repository or multiple? -
i using tortoisesvn manage couple of projects have on go @ moment. when first moved source control wasn't sure how should laid out ended putting each project own repository.
i wondering idea me move them 1 big repository , have them split project folders? else do?
at moment none of them share common code may in future. make easier manage if together.
thanks.
depends extent mean "project".
i have general local repository containing random bits of stuff write (including website, since it's small). single-user local svn repository not going suffer noticeable performance issues until you've spent lot of years typing. time svn faster anyway. i've yet regret having thrown in 1 repository, though of stuff in there unrelated other wrote all.
if "project" means "an assignment class", or "the scripts use drive tivo", or "my progress in learning new language", creating repos per project seems bit unnecessary me. again, doesn't cost either. guess i'd don't change you're doing. unless want experience of re-organising repositories, in case do change you're doing :-)
however, if "project" mean 'real' software project, public access repository, think separate repos per project makes sense: partly because divides things cleanly , each project scales independently, because it's people expect see.
sharing code between separate repositories less of issue might think, since svn has rather lovely "svn:externals" feature. lets point directory of repository @ directory in repository, , check stuff out automatically along stuff. see, always, svn book details.
Comments
Post a Comment