[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Set up advice please

From: Ryan Schmidt <subversion-2009b_at_ryandesign.com>
Date: Fri, 12 Jun 2009 05:54:52 -0500

On Jun 12, 2009, at 05:41, Zoe Cutting wrote:

> I am new to version control and have spent the last few days
> reading up
> on Subversion. I would like to hear others opinions on how they
> think I
> should set up my repository/repositories. Currently I work in a
> team of
> three developers although this is likely to expand in the future. We
> have three servers running different verisons of Coldfusion (6, 7
> and 8)
> and IIS. I'm thinking there are 3 possible ways I could set up.
> 1) Have each developer work on their local machine and commit their
> code
> to a central repository on one of the dev servers, the drawbacks I can
> see to this are having to have each local machine running all 3
> versions
> of Coldfusion which is possible but might prove impractical in the
> long
> run especially as new versions are released, also these machine aren't
> backed up which might create problems if someone forgets to commit
> their
> code and for some reason the machine goes belly-up.
> 2) Set up a repository on each of the dev servers and give each
> developer their own area on the server to work in, these servers are
> backed up so no worries about losing code. Is it practical to maintain
> three different repositories? What would be the drawbacks to this
> set up?
> 3) Set up one repository on one of the dev servers and as with option
> two give each developer an area on each server to work in and commit
> their code changes back to one repository. Can you see any
> drawbacks or
> impractibilities to using this method?
> I would be grateful for any thoughts or advice you have about these
> options. I want to make sure I set this up right to begin with to
> avoid
> problems in the future.


Option 1: Agreed, it can be difficult to keep multiple developers'
machines up to date with all required software.

Option 2: You don't want separate repositories unless they're for
completely separate projects that will never touch each other, and
even then you should consider whether it isn't easier to keep all
projects in a single repository.

Option 3: Sounds good, similar to what we used at a web development
company I worked at.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-06-12 12:55:59 CEST

This is an archived mail posted to the Subversion Users mailing list.