[CentralOH] Django Application Deployment and Production Delivery

[Michael Johnson]

As far as your question about database migrations and South: yes, absolutely. It does work a little differently than migrations in Rails, but I don't start a single Django project without using South. (In fact, the developer of South, who is also a core Django developer, is currently working on integrating the functionality into Django core directly: http://www.kickstarter.com/projects/andrewgodwin/schema-migrations-for-django )

Michael Johnson

Date: Thu, 18 Jul 2013 12:17:17 -0700

From: "Mark Aufdencamp" <mark at aufdencamp.com>
To: centraloh at python.org
Subject: [CentralOH] Django Application Deployment and Production
    Delivery
Message-ID:
    <20130718121717.181451e9c2a7ebbcd6ae28cea81146c8.21b0cd2c2c.wbe at email17.secureserver.net>
    
Content-Type: text/plain; charset="utf-8"

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/centraloh/attachments/20130719/dc4d27a5/attachment.html>