I\'m looking to hear some best practices...
Assuming a web application that interacts with a few different production servers (databases, etc.)... should the configu
In my Subversion repos for PHP, configuration files that contain passwords are checked in as config.php.sample with hints to what has to be provided and scripts relying require a config.php to be present at the same location.
The repository is configured to ignore config.php for that directory to avoid "accidental" adds or check-ins.