31st JULY - 4th AUGUST 2015

Pullman Brisbane - King George Square

Menu
Create Account
  • Mini-Conferences
    July 31
  • Presentations
    August 1-2
  • Sprints
    August 3-4

<-- Back to schedule

The one true way of doing Django deployments...

Project: Django

...doesn't exist. (Sorry)

The power and flexibility of Django comes with drawbacks. One of the toughest for project management is working out how to deploy your Django application. If you ask five different authorities on how you should do it, you'll get six different answers.

And if someone says "Just use fabric!": they're not helping.

Release management, dependency wrangling, virtualenv care and feeding; to .whl or .deb? To containerize or Heroku-ize? Do you really have to allow your servers unconstrained Internet access just to build your virtualenv?

As a Django user, you might end up writing more deployment solutions than Django projects. I know I have.

There's no one true way of doing Django deployments, but some work better than others. Maybe I can show you.

Tom Eastman

Tom Eastman is a developer, sysadmin, and teacher. He is a lead consultant for SafeStack Limited, a specialist security company that weaves secure best-practices into agile and fast growing organisations. Prior to that he was a technical lead and architect for Catalyst, New Zealand's largest company specialising in open source technology.