### Navigation

- index
- modules |
- next |
- previous |
- TurboGears 2.1.5 documentation »
- Search:
- Extended Table of Contents »
- Tips and Recipes »

# Deployment

Your code is somewhat useless if people cannot see it. This set of documentation describes how to deploy your TurboGears 2.1.5 application into a production environment, that is, an environment suitable for use by non-technical users.

Warning

Deploying a web application incorrectly can seriously compromise not just the application itself, but the entire server on which it is installed. If you are unsure about any process or idea, do not deploy until you are sure.

If you are new to web development, you should likely stick with the Standard Deployment Pattern. If you are an old hand, feel free to choose Alternate Deployment Patterns. TurboGears is extremely flexible in how it can be run and this documentation only begins to cover the available approaches.

- Standard Deployment Pattern
- Apache Web Server
- Apache Mod-WSGI
- Production Database
- Production Config
- Deploying Your Project Code
- Deploying your TG application with an Egg and Easy Install
- Optimizing Toscawidgets Resources

These sections describe non-standard approaches to deployment. You should not likely use these unless you are comfortable with web development and deployment or you have some particular need which is not met by the standard deployment pattern (above).

- Alternate Deployment Patterns
- Deploy with a Source Code Checkout
- Deploying as a Service/Daemon
- Running TurboGears 2.1.5 behind Apache with Mod Proxy
- FastCGI/WSGI – Running TurboGears 2.1.5 behind Apache
- Lighttpd and FastCGI
- NGINX Web Server

Todo

Document processes for repeatable local-only releases: Local PyPI, PIP, recordeggs, whole-virtualenv checkin/checkout.