> What are some sites using TurboGears 2.0 in a production setting? At Central Michigan University, we've been running a custom "housing reports" application since last July. Right now, it still runs on the alpha 1 release.
> Is the site Forward Facing or a backend? Forward facing, but it's part of a larger PHP site. You wouldn't be able to tell the difference between the Python-served pages and the PHP-served pages unless you looked at the server headers. > How is the site deployed? (mod_wsgi, mod_python, apache2, proxy, > paster, etc) Apache 2 with mod_proxy, but we're planning to switch to mod_wsgi. Getting things working under a 64-bit system was not a priority when we originally deployed, and mod_proxy was the quickest way to deploy. > What templating engine is used? (Genshi, Mako, Jijna, etc) Genshi is used, mostly because this project started with TG 1 right after the SQLAlchemy and Genshi changes came through. We switched to the alpha because of auth/auth issues. > How have web designers reacted to the constraints placed with the > templating engine you used? Web designers never touched the Genshi templates. A (very talented) designer created the site's design with XHTML and CSS, and developers turned that into the templates needed. Right now, there are both Genshi and Smarty templates for the site, which means differences pop up from time to time. > Are static files served by TG2? Nope, just by Apache. > How much daily traffic are you seeing? (hundreds, thousands, tens of > thousands) The app is only used by a handful of people, so probably less than fifty hits per day. > What type of hardware/hosting? (virtual, virtual machine, dedicated, > cluster, etc) Our operation runs Apple servers almost exclusively, and that's what the application runs on. > What implementation issues have you run into? Originally, I wanted to use Routes instead of object dispatch, but I gave up on that after a few hours. I'm sure the Routes stuff works a lot better than it did in the first alpha release. Not being able to configure Genshi's html rendering mode was also a huge pain. Trying to write your own repoze.who plugins for custom identity sources can be difficult as well, but I still like repoze.who more than the old identity system. Deploying the application on OS X Server was painful to say the least. This had a little to do with the order in which things were installed, a little to do with the fact that we decided not to use virtualenv, and a lot to do with Apple's crazy python deployment. > What steps have been taken to plan for the thundering herd? The site will probably never have more than ten concurrent users, but I do cache a lot of stuff. The queries we run for our reports can be pretty big. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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?hl=en -~----------~----~----~----~------~----~------~--~---
