[Chicago] deploying django apps, first steps for newbie

[sheila miguez]

Okay, let's say I have a site in production that is somewhat organized
according to this excellent blog post, <
http://michal.karzynski.pl/blog/2013/06/09/django-nginx-gunicorn-virtualenv-supervisor/
>.

For every new release, I could write something that fetches a tarball from
github for the release, makes a new virtualenv specific to that release,
and untars the repo following the convention in that blog post. I would
keep some number of old virtualenvs around for a while. That's my newbie
idea, and I'd like to know what best practices are for this kind of stuff.

More newbie questions:

worse practices
* how bad is it that I pip install things that require compiling on my
production box (psycopg2 for example)?
* how bad is it to install git on my production box?

Eventually I think I'll set up my own pypi. I think I could also try and
figure out how to make packages for things like psycopg2 so I don't need to
compile them. (assuming there is some reason I wouldn't want to use a
distro's package? is there?)


-- 
sheila
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/chicago/attachments/20131120/87e91087/attachment.html>