If you have multiple configuration files that must be used for different
environments, it might be best to have these in source control. For my
ASP.NET apps, I need a web.config file for my four environemnts (local
dev, shared dev, test, and production). What we do is create a
web.local.config, web.development.config, web.test.config, and
web.productions.config. When deployed, the appropriate file must be
manually renamed. This allows us to maintain a change history, yet not
accidentally deploy the wrong file version.
Hope this helps.
Michael Flanakin
-----Original Message-----
From: thomas Armstrong [mailto:tarmstrong@gmail.com]
Sent: Tuesday, November 29, 2005 6:26 AM
To: users@subversion.tigris.org
Subject: Re: How to make SVN not to manage one configuration file?
Thank you very much everybody.
2005/11/29, Erik Huelsmann <ehuels@gmail.com>:
> On 11/29/05, thomas Armstrong <tarmstrong@gmail.com> wrote:
> > Hi.
> >
> > I've got a configuration file within my project, which is different
> > on my PC and on my project server. So I want SVN not to manage it.
> >
> > How can I do it? Thank you very much.
> > --Thomas
>
> http://subversion.tigris.org/faq.html#ignore-commit
>
> HTH,
>
> Erik.
>
---------------------------------------------------------------------
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 Wed Nov 30 15:39:33 2005