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

Re: live and dev servers - best practices questions

From: William Nagel <bill_at_stagelogic.com>
Date: 2005-11-10 16:50:49 CET

On Nov 9, 2005, at 4:26 PM, Andrew Brosnan wrote:

> Hello,
> 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?

You might consider having four directories:


In dev_config and live_config, put files that can be read by the rest
of the site to get all necessary site-specific config information.
Then put the rest of your site in dev_branch/live_branch. On the
dev_branch and live_branch directories, set svn:externals properties
to point them to dev_config and live_config respectively. That way
you can easily merge the contents of dev_branch over to live_branch
without worrying that someone will accidentally merge development
site configuration information over to the live site.

> 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?

Yes, as long as you don't mind having the extra overhead of .svn
directories on your servers using working copies seems to be the best
approach to take.

> 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.

Well I wrote a book that covers a lot of SVN best-practices. It's
licensed under an open publishing license (much like the O'Reilly SVN
book), so you can get it in PDF form from Prentice-Hall's website
(link below), or you can buy a hard copy of it if you'd like.



> Regards,
> Andrew
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Nov 10 17:08:18 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.