Kevin Dangoor wrote:
On 12/7/05, Levi <[EMAIL PROTECTED]> wrote:
Kevin Dangoor wrote:
You're right... prod.cfg shouldn't be in svn. I wonder if there's a
convenient way to turn that off?
svn:ignore?
I was thinking something more along the lines of telling paster not to
add it in the first place. If someone *wants* prod.cfg in their
repository for some reason, I wouldn't want to stop them... it's just
not what I'd think of as default behavior.
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).
--
Ian Bicking / [EMAIL PROTECTED] / http://blog.ianbicking.org
