The Build Doctor

4 Comments

1. Evgeny wrote:

   I actually disagree that “He’d know”, he is the last person to know … if only because he is biased.

   Monday, January 26, 2009 at 8:26 am | Permalink
2. simpsonjulian wrote:

   We’re all biased, Evgeny. But if I find a Capistrano author writing a similar post, I’ll update

   Monday, January 26, 2009 at 8:49 pm | Permalink
3. Evgeny wrote:

   Also there is this new trend of replacing “puppet” with a more flexible dsl, it’s called “chef”, the new “hot” thing in ruby server cooking. So new I didn’t yet have a chance to check it out

   But capistrano is good at what it does, it copies files to a server and runs some commands — which is what a deployment system supposed to do. Puppet has a whole different purpose, it’s more of a “keep it so my servers have consistent behavior and configuration” kind of thing. It’s related to deployment, but not deployment itself.

   Monday, February 2, 2009 at 11:19 pm | Permalink
4. simpsonjulian wrote:

   Evgeny, I think that you, Andrew and myself all agree on this. Puppet for making sure that the server has all the dependencies that the app needs. Capistrano for deploying the application when you tell it to.

   Having been through Cfengine 2 and the birth of Puppet, I’m taking a rest before I look at Chef.

   Wednesday, February 4, 2009 at 2:27 pm | Permalink

Post a Comment