The last time we had a discussion about deployment was the Django Deployment Bonanza in January of 2011, and it was one of the most well-attended meetups. This suggests that deployment is a hot topic, or at least one that many find painful. A lot has changed in 1.5 years and we now have a plethora of deployment options for our Django projects.
I'll walkthrough the popular commercial PaaS offerings such as Heroku and Dotcloud as well as open source offerings such as Redhat's OpenShift and VMWare's CloudFoundry.
I'll also give a sneak preview of Appsembler, our cloud application platform built on Stackato, another commercial PaaS solution. Appsembler provides SaaS-as-a-service, meaning that we make it easy to offer your Django application as a hosted service including the billing of your customers.
If there's time we can also discuss using Fabric and Boto as well as Chef to deploy to IaaS providers such as Amazon or Rackspace. This way is not as sexy as using a PaaS, but for ultimate control and flexibility, one often needs to have full access to a server.
For background info on PaaS solutions for Django, check out this blog post that I wrote: