Oops, so I figured it out. We're not passing it in, we're manipulating it directly in cherrypy.config.
I'm planning to split out a new function update_server_config, which updates the server configuration data leaving update_config as is, but switching it to update the app config in cherrypy. --Mark Ramm On 2/28/07, Mark Ramm <[EMAIL PROTECTED]> wrote: > > Does anybody know how we are passing the config file to CherryPy prior to > the cp3 branch? I've read through config.py and startup.py and it doesn't > seem imediately apparent how we were configuring cp. > > And I need to update that process for cp3. Which should be easy enough, > if I can wrap my head around what we've done so far, and why we did it that > way. ;) > > -- > 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 -~----------~----~----~----~------~----~------~--~---
