Live data from Hacker News

Setup a complete Django server, deploy, rollback – all in one powerful script.

askthepony.com

11–14 of 14 posts

Re: Setup a complete Django server, deploy, rollback – all in one powerful script.

#11

I have a morbid fascination with improving my workflow and programming environment, so I absolutely adore combing through other developer's fabfiles. This one is definitely nicely put together, and there's some nice gems I look forward to adapting into my own. I'll say this though: while fabric is _ok_ at configuration management and provisioning new servers/instances, it's absolutely dwarfed by real tools for that k…

Agreed. There was a nice post on HN recently (http://news.ycombinator.com/item?id=2714149) about combining fabric + vagrant to manage django deploys. The vagrant part handles the "use puppet or chef" part of provisioning, while the fabric includes the "run quick commands on the VM" part after the VM is already provisioned. I learned a lot from that!

Re: Setup a complete Django server, deploy, rollback – all in one powerful script.

#13
post #10

I have a morbid fascination with improving my workflow and programming environment, so I absolutely adore combing through other developer's fabfiles. This one is definitely nicely put together, and there's some nice gems I look forward to adapting into my own. I'll say this though: while fabric is _ok_ at configuration management and provisioning new servers/instances, it's absolutely dwarfed by real tools for that k…

I've heard many good things about Chef -- seems to be the tool get job done. Could you guys share your Chef script/config so we can all benefit from learning by example?

Yes, I've often heard people say this is the way to go, but please blog about your own django server setup process using chef / puppet so we can see the details.

Re: Setup a complete Django server, deploy, rollback – all in one powerful script.

#14

This looks super nice. One thing I've found that really speeds up deploys using git (inspired by github's deploy process[1]), is having your production copies of your app just be a clone of the git repo. To deploy new code the commands that get run are just: $ git fetch origin $ git reset --hard origin/ A rollback is just: $ git reset --hard HEAD^ Fetching pulls down the new code, without replacing your production co…

[deleted]
Post reply on HN