On Sun, 2008-15-06 at 23:10 -0400, Mark Ramm wrote: > I removed a bunch of code from the TG2 project quickstart template. > in the config directory we had middleware.py, which setup the entire > middleware stack for your TG2 application. 90+ percent of the time > people are not going to mess with this, but we've already changed it > several times on users (in development), creating backwards > compatibility issues inside their templates. > > So, I've now got it set up to configure the middleware that needs to > be there automatically for you in the framework. Users who want to > take on the responsibility of managing their own wsgi stack can do so > easily enough, and beginning users don't have to worry about it at > all. > > My plan is to setup the environment.py file in the same way if there > are no objections. > > In both cases, there may be common configuration settings that we want > to address in the framework setup. I think the identity stuff that's > in there now provides a reasonably good example of what we can do. > > This should not break existing TG2 project's at all, because they will > just not use the new automatic setup stuff. But for new project it > will make upgrading from one TG version to another much simpler.
Sounds like a great plan to me! It's easy to forget how scary the config stuff is to new users. Iain --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
