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

live and dev servers - best practices questions

From: Andrew Brosnan <andrew_at_broscom.com>
Date: 2005-11-09 22:26:27 CET


I'm joining a project that is set up as follows:
* a development server (web and database)
* two load balanced 'live' web servers
* two database servers - (master/slave)
* an offsite 'failover' server - (web and database)

Currently things are a mess because data that should be specific to each
running version is included in the lone branch in the repository; so for
example, an update of the code on the dev server will result in the dev
server trying to connect to the live db rather than the dev db.
Typically, do you just store this type of data outside of the
repository? Or would you have a development branch and a live branch?

The code running both live (and dev) servers are working copies. I'm
told that this was done for the ease of just being able to run 'update'
after changes, thus updating the live (or dev) server(s). What do people
think of this? How do others ensure that your code is up to date in
cases where the code needs to run in multiple places?

I'd appreciate any advice or references to further reading to get me off
on the right foot. The subversion book is great, but I find myself still
wondering about many 'best practices' type things.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 9 22:27:55 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.