[Chicago] deploying django apps, first steps for newbie

Steven McGrath steve at cugnet.net
Wed Nov 20 18:47:15 CET 2013

I always use virtualenv out of habit (i’m staring at about 15 venvs currently active on my machine at the moment).  I’m not sure how usable it is to most people, but I even wrote a little script to help manage the virtual environments: 


Steven McGrath

On November 20, 2013 at 11:41:49 AM, Yarko Tymciurak (yarkot1 at gmail.com) wrote:

I am all for virtualenv for developing apps packages, or devel where you don't have a deployment target in mind.

Otherwise a virtual box cofigured with the target machine, and the development tree network mounted from your host is a scalable, distributeable solution, and a small step to deploying to the same environment.

edx is moving to doing this with ansible, and its a nice way to include / test other services & dbs.
See the wiki pages at github.com/edx/configuration

Vagrant & a vm are your friend.

On Nov 20, 2013 11:23 AM, "sheila miguez" <shekay at pobox.com> wrote:

On Wed, Nov 20, 2013 at 11:08 AM, Andy Boyle <andymboyle at gmail.com> wrote:
Sheila, have you ever used Fabric?


Not yet. My next step after figuring out what I want to have happen when I deploy things (like deciding whether I should run my own pypi, make completely new virtualenvs, etc.) is to decide on an automated config/deploy framework. One friend from ps1 suggested using puppet or salt if I have less than 100 boxes to worry about, chef if I had more.

To be honest, I only have one for now, and I am probably overthinking things due to my last job. On the other hand, the automation stuff will serve as documentation for myself 6 months later when I forget something, or for someone new who comes on.
As for installing git on your production environment, that's what we use to deploy our projects, so I'm not sure why it'd necessarily be a bad thing to have. I'd love to hear someone's arguments to the contrary.

I was trying to imagine some bad scenarios. sometimes gets partial access to things enough to do stuff with git or a compiler and then screws up everything. Though I suppose if they can compromise things enough to do that, they could probably sudo apt-get stuff. Though I don't have the user account the app runs under in the sudo group.

Just trying to think of bad crap. When I got my last job I tried to imagine how a defect might lead to someone's death. In an earlier job, a defect could likely lead to someone's death much easier than that job, so it became an interesting thought experiment. QA people are superheros who save us from horrible death and destruction.

Good luck!



Chicago mailing list
Chicago at python.org

Chicago mailing list  
Chicago at python.org  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/chicago/attachments/20131120/1730f3c7/attachment-0001.html>

More information about the Chicago mailing list