Svn ignore versioned on update?

I would suggest renaming the file in the repository from config. Php to config.php.sample. This is the file that you would edit to change the default options.

For deployment, either to your development environment or to the production server, you would copy config.php. Sample to config. Php and edit it without worrying about future conflicts.

Don't forget to ignore config. Php after doing that. – Mauli Sep 22 '08 at 9:43 thanks for the great tip!

I was really thinking of this because this is the only file that change per environment – ken Sep 22 '08 at 9:48 We have the same problem at work and I still don't get it why a config that is dependent on the environment is actually in a repository. – unexist Sep 22 '08 at 10:03 the convention is usually to call it config.php. Tmpl (for template) – Avi Sep 22 '08 at 12:35.

Another solution is maintaing all the configuration files for every environment in SVN. Depending on the value of an environment variable, only some files are used. Advantages: 1.

All files in SVN. 2. No copy of files in deploy/checkouts/updates... Disadvantages: 1.

All files in SVN. 2. There is an environment variable.

An alternative workaround is to use the tsvn:ignore-on-commit property. It will make files always start off unchecked in TortoiseSVN's commit dialog. If you'd want to commit it, you need to manually check it.

tortoisesvn.net/docs/release/TortoiseSVN... (bottom of the page).

This document talks about a changelist, not a property. Do you have a reference to a property that sets this changelist or something? – Bert Huijben Oct 8 '08 at 13:27.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.