[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: controlled files to be deployed to different environments

From: Karl E. Jorgensen
Subject: Re: controlled files to be deployed to different environments
Date: Wed, 21 Aug 2002 22:39:59 +0100
User-agent: Mutt/1.3.28i

On Wed, Aug 21, 2002 at 12:52:06PM -0500, Daniels, Dave F wrote:
> For one of my projects I have a configuration file, say,
> which I'm versioning in CVS. The contents of this file will be different for
> different environments, though. For example, the mail server for my
> development environment is different than for my production environment.
> Currently, I have the development version controlled, and when my project is
> ready for deployment to production, I manually change the contents and send
> it off (but don't change the version in CVS). I would like suggestions on
> ways to control different versions of the same file. So far, the best idea
> we've come up with is to give each version a different extension and then
> use our make utility to pull the right one and rename it, so
> becomes Any other suggestions?

Not really something for CVS to do...

But: Why not then maintain separate *patch* files for each environment?
It should then be possible to apply the relevant patches through your
build system; only needing manual intervention when something doesn't
apply cleanly (similar to CVS conflicts).

Karl E. Jørgensen
==== Today's fortune:
If an experiment works, something has gone wrong.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]