Ian Bicking <[EMAIL PROTECTED]> writes: > Personally I'm inclined to name all configurations, including prod.cfg, and > keep them... somewhere. Maybe in a config/ directory or something. Then if > you add some configuration parameter, you can add it to all configuration > files at once. And instead of saying "yes, production now" or "no, not so > much", you instead say "use 'prod'". For instance, I typically have three > configurations at least: one for deployment, one for interactive development, > and one for unit testing (the unit tests wipe everything on each run, which > I'd rather not happen to my interactive development environment).
There's also the problem of keeping other configuration files, such as Apache's vhosts. I believe that a 'conf' directory would be handy for this kind of organization. Be seeing you, -- Jorge Godoy <[EMAIL PROTECTED]>
