I'm not arguing that this is the best way, but as a data point, here's what I do.
I use buildout to generate app.ini, as well as other config files, including for uwsgi and supervisord, from templates (using collective.recipe.template.) I have several top-level buildout config files, all of which specialize a common basic configuration: one for deployment, one for staging, one for development. All of the twiddly bits (API keys, paths, logging config, etc.) are in one place (the top-level buildout config file), and it is quite flexible (e.g. uwsgi for deployment, pserve for development.) On Sat, Nov 7, 2015 at 6:46 PM, Eric Hanchrow <[email protected]> wrote: > On Sat, Nov 7, 2015 at 12:56 PM, Jonathan Vanasco <[email protected]> > wrote: > >> >> >> On Saturday, November 7, 2015 at 12:22:40 AM UTC-5, Mike Orr wrote: >>> >>> The ideal way would be to have a different INI file for different kinds >>> of deployment >>> >> >> I used to believe that... but as projects progressed, ini files got >> larger and more difficult to maintain. It's hard enough keeping >> Production/Staging/Dev in step with one another. >> >> Splitting this out into "production-admin.ini" and >> "production-non_admin.ini" files to declare a single variable would mean >> having another file to update whenever other ini settings change. >> >> I assume that this is exactly why http://12factor.net/config says " > Store config in the environment". > > -- > You received this message because you are subscribed to the Google Groups > "pylons-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/pylons-discuss. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/d/optout.
