Edited by dhinged, 17 February 2013 - 06:42 PM.
Posted 17 February 2013 - 06:40 PM
Posted 17 February 2013 - 06:55 PM
There's no reason why the "common" parts could not be versioned in one file, and the server/site/whatever-specific parts (which could probably also be versioned too!) could not be added to the file during the build/deploy phase.
Edited by salathe, 17 February 2013 - 06:57 PM.
Posted 17 February 2013 - 08:30 PM
Eg, for my site config files, I'd have a file in the repo that is named: config.inc.php.base which contains all the config directives w/ default or empty values. Then whenever setting up an environment that file is just copied to config.inc.php and customized with the proper values.
The same concept could be applied to your .htaccess file, or any other files that need site-specific changes.
Did I help you out? Feeling generous? I accept tips via Bitcoin @ 14mDxaob8Jgdg52scDbvf3uaeR61tB2yC7
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users