SitePoint Sponsor

User Tag List

View Poll Results: you?

Voters
3. You may not vote on this poll
  • 1 repo for each project

    1 33.33%
  • all projects in 1 repo

    2 66.67%
Results 1 to 5 of 5
  1. #1
    SitePoint Enthusiast
    Join Date
    Sep 2008
    Posts
    38
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    1 project = 1 repo ?

    Hi,

    what is better - to have 1 svn repo for each project,

    or to have 1 repo with all projects..

    Right now I have all of my projects in one repo (im kinda new to svn), and it's quite messy to show timeline with all of the projects..

    what layout do you have ?

  2. #2
    SitePoint Evangelist
    Join Date
    Aug 2007
    Posts
    566
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    I have everything stuffed under 1 repo.
    Probably an old habit from my CVS times. And I find it more practical to backup and restore too.

  3. #3
    <?php while(!sleep()){code();} G.Schuster's Avatar
    Join Date
    Mar 2007
    Location
    Germany
    Posts
    428
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    I have at least one repo per project - sometimes there are multiple repos per project for different parts of the project.
    See...if you've got only one repo for all projects all of your projects share one revision number.
    Why would you want to do that?
    You can't tell whether a specific project is _really_ revision "xy" or it has this revision because any of the otehr projects has changed.
    The other things is repo-backup or re-location.
    What if you want to extract one repo and set it up on another server? Or the customer requests a copy to set it up on his own server for further development?

    I could go on for years...to cut a long story short - there are nearly no cons for "one project, one repo" but many, many pros.

  4. #4
    SitePoint Evangelist
    Join Date
    Aug 2007
    Posts
    566
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    See...if you've got only one repo for all projects all of your projects share one revision number.
    Why would you want to do that?
    See it the other way: why would I always want to track my application by revision numbers ?

    When 1 project hit a milestone, I tag it. I think that the milestones, not the commit revisions, are more close to my way of working. I sometime commit a file just because I had edited it on my laptop, or on one of my 4 regular computers.
    I mostly use svn as a way to keep track of changes, and not to worry about which version is the last one.

    Some other projects, I use the date as the reference. I don't necessarily want a specific version, but I want the application in it's state at a precise date.

  5. #5
    . shoooo... silver trophy logic_earth's Avatar
    Join Date
    Oct 2005
    Location
    CA
    Posts
    9,013
    Mentioned
    8 Post(s)
    Tagged
    0 Thread(s)
    I used to put all my projects under one SVN repository. However I stopped doing that after I started to decouple the components of my personal framework making each one independent. I give them there own repository to keep track of them easier.

    If you need those pieces of other repositories in one of your projects you can use SVN:External.
    Logic without the fatal effects.
    All code snippets are licensed under WTFPL.



Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •