We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Django Deployments Done Right

Formal Metadata

Title
Django Deployments Done Right
Title of Series
Part Number
12
Number of Parts
46
Author
Contributors
License
CC Attribution 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
There's no single standard toolkit for deploying Django sites. In our years of consulting, we've seen lots of deployment systems in the wild and where they break down or cause pain. Independent of the system you use (Salt, Ansible, Fabric, Chef, Docker, etc.), there are a few principles a good deployment should follow: Deployments don't take the site down or interrupt active users on the site. Deployments don't involve more than one step or are completely automated. Deployments are fast. A failed deployment never takes down the current running version of the code. Rolling back to a previous deployment is a single step. By following these principles, deployments go from being error-prone, nerve-wracking experiences to trivial non-events in your daily development cycle. This talk will walk you through the steps necessary to create a better deployment process.