> I'm torn on whether or not to use dev-specific config files onto have > dynamically loaded config sections of a single config. > > I wouldn't feel terribly comfortable doing *too* much hackery by way of > precompiling config dynamically.
> That said, having it explicitly load a boss-dev.config or something like > that would probably be the simplest change to add prod/dev config splits. Yeah, as I said in my other email, I'd be happy to get away from having CB be so dependent on weird compiler hacks, and do things in a more Erlangish way. Rather than have completely separate files though, what I'd ideally like to see is have values from the dev or production files override the main config file, so that most of the configuration can be centralized and only bits and pieces customized as needed. -- David N. Welton http://www.welton.it/davidw/ http://www.dedasys.com/ -- You received this message because you are subscribed to the Google Groups "ChicagoBoss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at http://groups.google.com/group/chicagoboss. To view this discussion on the web visit https://groups.google.com/d/msgid/chicagoboss/CA%2Bb9R_tMc4HyuftTQUAjHsCZrQfGPC3Q9oC6sxbvqnVacY8rtQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
