Deployment, configuration, and testing are fast-moving targets. This chapter was written with the most stable deployment scenario in mind, but you can find a lot more about configuring and deploying you applications at www.turbogears.org, and www.turbogearsbook.com
TurboGears prod.cfg contains all the production-specific configuration settings for your application. Often, all you have to do is edit this file to point to the proper location of your production database.
The benefits of placing your TurboGears application behind Apache or IIS include HTTP 1.1 support, improved handling of buggy requests, and you can use "virtual hosting" to easily set up multiple TurboGears applications behind a single front-end web server.
When you use mod-proxy or mod-rewrite you are responsible to monitor the Cherry-Py server to make sure that it gets started when the web server starts, and restarted if something should happen. We've included a little CGI script that starts your application whenever a user would otherwise have received a 502
The main advantage of mod-python is that everything runs in Apache, so you don't have to monitor another process. The main disadvantage is that Apache needs to be restarted whenever you change your application code (and on shared hosting, it's not likely you'll be allowed to start and stop Apache at will).
TurboGears applications scale out to the extent that you use cookies and database storage rather than in-memory sessions.
