# Svn repositories with multiple projects - best practice?

**URL:** <https://www.ruby-forum.com/t/svn-repositories-with-multiple-projects-best-practice/126119>\
**Category:** Rails\
**Created:** [January 15, 2008, 4:28pm UTC](https://www.ruby-forum.com/t/svn-repositories-with-multiple-projects-best-practice/126119 "2008-01-15T16:28:36Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![blinking\_bear](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/a9a28c/32.png) [@blinking\_bear](https://www.ruby-forum.com/u/blinking_bear)\
**Post date:** [January 15, 2008, 4:28pm UTC](https://www.ruby-forum.com/t/svn-repositories-with-multiple-projects-best-practice/126119/1 "2008-01-15T16:28:36Z")

</div>

Quick svn question - sorry this rails related.

If I setup a repository once and then add multiple projects using ‘svn  
import’ is it correct that all the projects share they same revision  
numbers? Is this expected? It seems kind of confusing that way.

On the other hand, if I use ‘svnadmin create’ to create a single project  
repository for each project that seems like overkill. What is the best  
practice here?

---

<div class="post-metadata">

**Author:** ![blinking\_bear](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/a9a28c/32.png) [@blinking\_bear](https://www.ruby-forum.com/u/blinking_bear)\
**Post date:** [January 15, 2008, 4:43pm UTC](https://www.ruby-forum.com/t/svn-repositories-with-multiple-projects-best-practice/126119/2 "2008-01-15T16:43:58Z")

</div>

I’ve been thinking about this recently and would like to hear what  
other people think. I’m leaning towards a new repository for each new  
project, but not sure.

DAZ

---

<div class="post-metadata">

**Author:** ![blinking\_bear](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/a9a28c/32.png) [@blinking\_bear](https://www.ruby-forum.com/u/blinking_bear)\
**Post date:** [January 15, 2008, 4:51pm UTC](https://www.ruby-forum.com/t/svn-repositories-with-multiple-projects-best-practice/126119/3 "2008-01-15T16:51:02Z")

</div>

On Jan 15, 2008, at 10:28 AM, blinking bear wrote:

> Quick svn question - sorry this rails related.
> 
> If I setup a repository once and then add multiple projects using  
> ‘svn import’ is it correct that all the projects share they same  
> revision numbers? Is this expected? It seems kind of confusing  
> that way.

Expected? Yes. Confusing? Well, if your experience is with SCS, CVS,  
RCS, etc. where each file has its own revision perhaps.

> On the other hand, if I use ‘svnadmin create’ to create a single  
> project repository for each project that seems like overkill. What  
> is the best practice here?

Not overkill. This will make sense once you start using it. In fact,  
if you look at Rails itself, you see that it is actually rails,  
active\_support, action\_pack, active\_record, (action\_mailer,  
action\_web\_service, …) and each has its own repository (somewhere).  
You don’t generally have to worry about that since the dependencies in  
RubyGems takes care of getting all the parts when you ask for Rails.

I typically have an ./svn directory under which I create  
repositories. For real “projects”, a separate repository is created,  
but I have a bunch of random stuff in a repository called “code”

-Rob

Rob B. [http://agileconsultingllc.com](http://agileconsultingllc.com)  
removed\_email\_address@domain.invalid

---

<div class="post-metadata">

**Author:** ![blinking\_bear](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/a9a28c/32.png) [@blinking\_bear](https://www.ruby-forum.com/u/blinking_bear)\
**Post date:** [January 15, 2008, 5:00pm UTC](https://www.ruby-forum.com/t/svn-repositories-with-multiple-projects-best-practice/126119/4 "2008-01-15T17:00:29Z")

</div>

On 15 Jan 2008, at 15:28, blinking bear wrote:

> Quick svn question - sorry this rails related.
> 
> If I setup a repository once and then add multiple projects using  
> ‘svn import’ is it correct that all the projects share they same  
> revision numbers? Is this expected? It seems kind of confusing  
> that way.  
> it is expected

> On the other hand, if I use ‘svnadmin create’ to create a single  
> project repository for each project that seems like overkill. What  
> is the best practice here?

I’ve always used a single repository. Easier to maintain and all that  
(and if you do ever need to do any cross project operations, you’re  
basically stuffed if they’re not in the same repository) and not much  
in terms of downsides.

Fred