Deploying Your Project Code

There are a number of ways you can deploy your application’s code in production. While there is an “officially” standard way to deploy (via eggs), that pattern is not universally accepted.

Your application’s code is likely to be the most frequently changed component of your application (compared to the libraries that make up TurboGears), so you will likely re-deploy your code many times, possibly many times per day.

• Deploy with an Egg – which can be installed via easy_install or PIP into your Application-Specific VirtualEnv with the Production Config being the only file in the deploy_modwsgi_deploy directory (/usr/local/turbogears/myapp/ by default)
• Deploy with a Source Code Checkout (often of a branch or a tag) directly into the deployment directory by the www-data user. Note that this requires some changes to your .ini file!

What’s Next?

• Standard Deployment Pattern provides an overview of the standard deployment process