Sorry it was late, and was both confused, and said what I meant in a confusing way.
What I'm talking abut is a way to parse our old config files to pass into cherrypy as required. Right now we have a central config system, which is only passing stuff to cherrypy's global config. We need to parse it differently and pass it to the cherrypy global config, and app.cfg. But the real question (as Kevin noticed, in spite of my obtuseness) is how we deal with the tree/app config split. Mounting sub-applications in trees is one of the main things we need at my work, it would be great if we could work this out in a way that let's us be backwards compatable with our old config file format. --Mark On 2/27/07, Robert Brewer <[EMAIL PROTECTED]> wrote: > > Mark Ramm wrote: > > So now that CherryPy config is pretty much global > > config only, any thoughts on how we should best > > manage configuration files in TurboGears 1.1 in > > order to provide some level of backwards > > compatibility to our users? > > I'm not sure what you mean by "global config only"...? There's global > config, app config, and "tree config" (_cp_config), which get merged > into request.config. > > > Robert Brewer > System Architect > Amor Ministries > [EMAIL PROTECTED] > -- Mark Ramm-Christensen email: mark at compoundthinking dot com blog: www.compoundthinking.com/blog -- Mark Ramm-Christensen email: mark at compoundthinking dot com blog: www.compoundthinking.com/blog --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
