在aws上运行django项目的最佳方法是什么？

Question

How should the project be deployed and run. There are loads of tools in this space. Which should be used and why?

• Supervisor
• Gunocorn
• Ngnix
• Fabric
• Boto
• Pip
• Virtualenv
• Load balancers

Answer 1

It depends on your configuration. We are using the following stack for our environment on Rackspace, but you can setup the same thing on AWS with EC2 instances.

• Ubuntu 11.04
• Varnish (in memory cache) to avoid disk seeks
• NginX to server static content
• Apache to server dynamic content (MOD-WSGI)
• Python 2.7.2 with Django
• Jenkins for our continuous builds
• GIT for version control
• Fabric for the deployment.

So the way it works is that a GIT push to the origin repository is being polled by Jenkins. Jenkins then pulls the changes down from the origin. Builds a Python Egg, runs Unit tests, uses Fabric to deploy this egg to the environments necessary and reloads the Apache config to make sure the forked Apache processes are picking up the new Python egg.

Hope this helps.

Answer 2

As Michael Klockel already stated depends on your configuration, I have:

• Ubuntu 10.04 LTS
• Nginx
• Uwsgi
• git version control
• python virtualenv and pip

You can check the deployment settings here: Django, Virtualenv, nginx + uwsgi import module wsgi error

and why I use nginx and uwsgi here: http://nichol.as/benchmark-of-python-web-servers

Also I use fabric for the deployment of the app, and chef solo http://ericholscher.com/blog/2010/nov/8/building-django-app-server-chef/

johny cache for sql queries and raven and sentry to keep a log of whats going on on the app.

Answer 3

I'd use uWSGI+Nginx from a performance perspective (I think the comparison has already been linked in another answer), pip and virtualenv for deployment as this keeps things self-contained, and facilitates clean deployment using fabric or similar. Use git for version control. Jenkins can handle continuous integration. I'd use the AWS load balancer (ELB) in front of your EC2 instances for balancing - does the job without you having to fret too much about it. django-storages for uploading your static files to s3, that saves you the effort of having another server to hand out static files.

However, it depends a little on your admin overheads. If you're looking for something clean and simple for deployment and scaling, I'd scrap the whole AWS EC2 stack, use Heroku as a front end, and s3 for your static files. This saves all the admin time of maintaining the boxes, and allows you to concentrate on the dev.