Seconding Fabric. Fast, easy, and friendly deployment. I've been in RPM hell rolling a deployable django app. Total overkill IMO but business rules are business rules.
Trace On Wed, Jun 13, 2012 at 3:05 PM, Toby Champion <[email protected]>wrote: > I'd recommend using Fabric over Chef if your application is in Python. > That's because you can use your application code, either some of the Django > project itself or your libraries, from within Fabric. I've found this > useful for testing and diagnostics. I've used it recently for throwing fake > data at an XMPP server, by using a library that's used by the Django app > directly from Fabric. You can do this sort of thing by writing Django > management commands, but for quick and dirty work (often required of > start-ups), it's easier from Fabric. > > Also, it's one less language to be programming in every day. > > Toby > > > On 6/13/12 1:53 PM, Adam Feuer wrote: > >> On Wed, Jun 13, 2012 at 12:39 PM, karen<[email protected]> wrote: >> >>> There's Paste, which >>> doesn't sound ideal.....what else should I be looking at? >>> >> It's not Python, but it's really good for this: Chef >> http://www.opscode.com/chef/ >> >> It has a good community and a lot of pre-built recipes (scripts). I've >> used Fabric and Chef, I count those big advantages over Fabric. >> >> More info: >> >> http://www.opscode.com/blog/**2011/05/23/deploy-django-cms-**with-chef/<http://www.opscode.com/blog/2011/05/23/deploy-django-cms-with-chef/> >> >> http://wiki.opscode.com/**display/chef/Build+a+Django+**Stack<http://wiki.opscode.com/display/chef/Build+a+Django+Stack> >> >> -adam >> >
