Whether you use distutils, git, tar, deb, or rpm doesn't matter; the packaging is really a small part of the deployment process. You still have to distribute your application, as well as provision the server with your dependencies, make sure the necessary services are running, etc.
You could just as easily use Fabric to deploy an RPM as you could an untarred directory. I highly recommend Salt (http://saltstack.org/). It has a remote execution model that is way more efficient than using Fabric to SSH into a bunch of machines. It makes configuration management incredibly easy because it does not try to invent a new DSL. The coolest part is that it is 100% Python and incredibly easy to write your own modules for. On Thu, Jun 14, 2012 at 12:36 AM, william <[email protected]> wrote: > I actually prefer using the systems native package management system. It's > the best way to make sure you aren't missing any dependencies. > > It's also easy if you already have a setup.py which produces the correct > package format (rpm, deb, etc) and make the packages as part of your > continuous integration builds. > On Jun 13, 2012 8:07 PM, "Trace Peters" <[email protected]> wrote: > >> 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 >>>> >>> >>
