On 29 jan 2007, at 19.36, Cliff Haithcock 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)?
>
> Regards,
> Cliff
>
>
A viable solution is to not have a checked in configuration script,
but instead use a checked-in configuration script template.
Mark the place where for example the database url occurs in some way
so that a perl or mzscheme script can generate platform specific
configuration scripts from the template.
------
What is a woman that you forsake her, and the hearth fire and the
home acre,
to go with the old grey Widow Maker. --Kipling, harp song of the
Dane women
Tommy Nordgren
tommy.nordgren@chello.se
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jan 29 21:32:39 2007