On 1/29/07, Cliff Haithcock <cliff@rasantiago.com> wrote:
>
> Hi all,
>
> I reviewed the FAQ and searched through the archives for info on using
> Subversion to manage website development. I could not find an answer to
> the following situation.
>
> We have a production db server, staging db server, and development db
> servers for our developers. We plan to have developers checkout from the
> trunk and set the staging and production environments to serve from
> checked out tags.
>
> Within each of the three development environments, we modify the db
> connection script to point to the proper db server.
>
> We are looking for a best practices solution for how to manage a file in
> svn that our current setup requires to be different upon the usage of
> the checked out code.
>
> Do we pull the one db connection script out of svn and manage it
> manually? Or is there some clever way to drive svn to solve our problem?
> Or should we make our connection script smart enough to know which db
> server it should connect to (we aren't exactly sure how to do this, but
> will consider it)?
The last is the option I always opt for. That or a configuration file
specific to each environment, which is loaded based on code detecting
the environment it's running in. This way, I can be certain that I am
always moving the exact same code into each environment.
IOW, I don't want to change *anything* when I move my application from
one environment to the next. It should be smart enough to detect
where it's running, and how it should configure itself.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jan 29 19:45:50 2007