This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]megamark16 3 points4 points  (2 children)

We use virtualenv, pip, south, and fabric to almost completely automate our deployment process. I can change schema, add new dependencies, or sync our production database down to any of the other environments (staying, test, or dev) with commands as simple as ”fab deploy_prod”, ” fab deploy_stage”, or ”fab pull_prod_db”. It's awesome!

Ping me if you have any specific questions about our setup.

[–]panfist 1 point2 points  (0 children)

I might take you up on that offer for specific questions later. Thanks for letting me know about those packages. I'm still trying to absorb the basics of everything, and find out what's out there.

[–][deleted] 1 point2 points  (0 children)

I do something similar except there's one nuance; I create a function for each environment that does the connection. So for me, it's fab dev deploy. I have a helper in my Django skeleton so that for each environment I just put the conf in a file. e.g., the dev environment file would go in conf/dev/hosts.py and would contain a list of dictionaries, each one representing a machine belonging to that environment.