Deploying Django

Presenting my setup at LA Django Meetup Feb. 21, 2012.

Transcript

1. DEPLOYING DJANGO Brian Riley @btriley
2. DEPLOYING DJANGO or, you could just use Heroku Brian Riley @btriley
3. WHO AM I? • been working with Django since 2006 • put Django into production many times, using just about every setup • work at EdgeCast
4. DEPLOYING IS CONFUSING • gunicorn or uwsgi • nginx or apache • ? or ? or, you could just use Heroku
5. THE STACK
6. THE STACK: WEB SERVER • serving static media files • proxying to dynamic applications “nginx is an HTTP and reverse proxy server”
7. NGINX CONF server { listen 80 default; server_name example.com; location /static/ { root /path/to/project; } location / { proxy_pass http://127.0.0.1:8000; } }
8. THE STACK: WSGI SERVER “Gunicorn 'Green Unicorn' is a Python WSGI HTTP Server for UNIX” ./manage.py run_gunicorn
9. UPSTART • comes with Ubuntu • automates startup/shutdown of processes • use to manage your gunicorn service: service gunicorn [start | stop | restart]
10. description "Gunicorn for my Django application" start on runlevel [2345] stop on runlevel [!2345] #Send KILL after 5 seconds kill timeout 5 respawn env PROJECT_ROOT="/opt/my_django_app" script exec python $PROJECT_ROOT/portal/manage.py run_gunicorn -- settings=settings.production --preload -w 16 --log-level debug --log- file /var/log/my_django_app/gunicorn.log -p /var/run/gunicorn.pid end script /etc/init/gunicorn.conf
11. AUTOMATION: FABRIC • command-line tool for running remote shell commands • fab deploy
12. QUESTIONS? @btriley yes, you could just use Heroku