> > Well, you don't put those "certain files" in SVN. Where files contain > information that is specific to the environment, you create sample files > and check THOSE in, which the person checking the code out can copy, > rename and modify. > For example, if you have an settings.php file that contains a whole > bunch of configuration information, you should first put settings.php as > an svn:ignore item, so that it doesn't ever get checked in (this > prevents some other developer's settings file from overwriting yours), > and you should create a settings.php.sample file which contains a sample > set of configuration settings which a developer can copy and rename to > settings.php and change to suit their own environment.
I use this pattern quite a lot. What I generally do, is store separate config files for each environment in a development directory in SVN, then run an install script that copies the file into place to set up the environment. eg: dev/config/local.config.php dev/config/staging.config.php dev/config/live.config.php These get copied to a config.php that is linked from the actual application, but is never checked in to source control. Regards, Mark --~--~---------~--~----~------------~-------~--~----~ NZ PHP Users Group: http://groups.google.com/group/nzphpug To post, send email to [email protected] To unsubscribe, send email to [EMAIL PROTECTED] -~----------~----~----~----~------~----~------~--~---
