Hi List, We have a couple pylons-based projects that we distribute along with configuration files for production, development, and testing. Some of the values in these files are specific to the machine that they are installed on, which means when we update from version control, we have to merge the changes. It would be nice to have the machine-specific values in a different file that wasn't source controlled. Is there a convention around this? Maybe our current configuration file usage is wrong?
Any relevant documentation or personal experiences would be appreciated. Thanks -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
