[CentralOH] Django Application Deployment and Production Delivery

Thomas Winningham winningham at gmail.com
Thu Jul 18 21:30:35 CEST 2013

I can answer a couple of things:

1. Check out UWSGI (or micro wsgi) ... a lot of fun! You could
reverse-proxy it behind Apache or Nginx  for instance. I guess I'm thinking
of this the way IHS & WebSphere work, but I'm more familiar with that
(Java) type of stuff, so ignore this rabbit hole possibly.

2. For automation of deployments and such try Fabric or Ansible. I have
some Fabric stuff, but I'm converting it to Ansible I think soon.

3. There are Python GIT stuff that is developing and exciting, but you can
do all that with #2, and I do.

I also like Nose for testing, or at least I did when I did TDD, and having
taskbar notifications of pass/fail upon saving was a very cool feature.

Hope this helps, and I'll definitely be reading other replies myself too :D

On Thu, Jul 18, 2013 at 3:17 PM, Mark Aufdencamp <mark at aufdencamp.com>wrote:

> Hi All,
> While many of you here are busy planning the upcoming PyOhio, I've been
> engaged in learning to coherently converse on TDD and Django this year.
> I've been following O'Reilly's "Test Driven Development in Python" which
> is still sparse on chapters.  I've managed to complete the first three
> chapters of building an application.   In preparation of deploying to a
> server, I stepped back into some virtualenv/pythonbrew learning and
> discovered the magic of PythonPath and the site_packages directory.
> I've learned a bit and can successfully configure a venv and utilize it
> for development.
> I'd now like to propagate that to a production environment.  I've ruled
> out mod_python as an option to run django apps.  That leaves wsgi and
> gunicorn.
> So, I guess I'm looking for someone with some experience utilizing
> apache/wsgi/venv/django to give me some sage advice on how they do it
> and the gotchas?
> Alternatively, if your running NGinx in front of gunicorn with BSD
> sockets, I'd be really interested in hearing of your experiences. (I
> like the performance and no TCP port requirement)
> In conjunction with selecting and building a production platform, I'm
> curious as to the differing deployment methodologies utilized in the
> group.  I'm spoiled by capistrano in the ruby world.  Any great
> equivalent in the django world?  Utilizing scp/sftp?  Pulling with
> git/svn directly from a repository?
> How about dealing with database migrations in django?  Anyone utilizing
> South?
> Last question, anyone utilizing Hudson with django/venv as a testing
> platform?
> Hoping to elicit some responses, and looking forward to this years
> PyOhio.
> Mark Aufdencamp
> _______________________________________________
> CentralOH mailing list
> CentralOH at python.org
> http://mail.python.org/mailman/listinfo/centraloh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/centraloh/attachments/20130718/af390555/attachment.html>

More information about the CentralOH mailing list