Dan Levine ha scritto:
> I would love to hear other replies on this as well.
>
> The way we handle a similar situation is through an Ant Replace task in the
> build script. Assuming you run:
>
> svn update
> ant compile
>
> The second step can be used to pull values from a (local server specific)
> data file and replace placeholders (%DBNAME%) with the actual values. That
> specific file does have to live outside of SVN though. (Or you could check
> them all in with different names, and use an environment variable on each
> server to specify to ant which to use, but that is a bit muddy imho.)
>
> Dan
>
> -----Original Message-----
> From: Andrew Brosnan [mailto:andrew@broscom.com]
> Sent: Wednesday, November 09, 2005 1:26 PM
> To: users@subversion.tigris.org
> Subject: live and dev servers - best practices questions
>
> 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?
>
> 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.
>
> 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
>
>
I keep the dev. version of the code in /trunk and the production version
in /branch/prod.
The production branch was made by copying the trunk when I felt it was
ready for production, and then by changing a few config parameters so
that the application pointed to the prod servers.
Now whenever I make a change to /trunk that I feel I want in production
too I just merge the affected files.
HTH
--
Marcello Romani
Developer
Spin s.r.l.
Reggio Emilia
http://www.spinsoft.it
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Nov 10 09:14:32 2005