Capistrano gets competition: Vlad the Deployer
We talked to part of the Ruby Hit Squad about their motivations to create Vlad the Deployer. Following the information on the website, the first question was whether Vlad is simpler than Capistrano:
Eric Hodel: Not so much simpler as less complex and easier to understand and maintain.Note: Flog is a tool that looks at Ruby code and determines how "tortured" it is, with higher scores indicating higher levels of pain. The tool uses Ryan Davis' ParseTree library to analyze the Ruby code (in ParseTree's AST form). It checks various aspects of the code, among them the use of methods like
Wilson Bilkovich: Not just simpler code, but a simpler user experience as well. I have occasionally had serious difficulty 'handing off' a Capistrano config to a customer at the end of a project. Vlad is less complex in an empirical way. We frequently decided on an approach by using 'flog' and picking the code with the lowest score.
EH: We also wanted the most common deployment operations built-in making it easy for most users to get up and running. At the last Seattle Ruby Brigade meeting Geoff Grosenbach sat down to learn vlad expecting to take all night. He was done in about 5 minutes.
Ryan Davis: Yeah, we're trying to give basically the same amount of functionality, but with much less complexity:
Flog (1.1) Scores:
net-ssh-1.1.2.gem : 7528.3
needle-1.3.0.gem : 1685.4
capistrano-2.0.0.gem: 5609.2 (nearly 6x more than vlad)
TOTAL = 14822.9 (more than 3x more than vlad + deps)
open4-0.9.6.gem : 742.0 (and we really only make use of 1 method)
rake-0.7.3.gem : 3208.9 (this includes contrib)
vlad-1.0.0.gem : 945.5
TOTAL = 4896.4
eval, hooks like
method_added, use of open classes and other concepts that have the potential to increase complexity..
The Ruby Hit Squad continues with more reasons for creating Vlad:
RD: A few reasons:
1) Understanding cap, Net::SSH, and needle was way too hard for me. I'm simply allergic to clever code these days.
2) Net::SSH had way too many problems to be used as an actual SSH client.
3) It took me hours to diagnose some Net::SSH problems and all I got in response was basically "*shrug* SSH is wacky".
4) Finally, deployment is always last and always under pressure and you shouldn't have to have so many problems with it. It should Just Work(TM).
EH: Capistrano sits on a large stack of software and is deeply coupled to it. We wanted something simple and understandable. We chose to sit on top of rake because its much more familiar and is much easier to understand.
WB: If my only problems with Capistrano were a few bugs, I would have submitted patches. I wanted a deployment toolkit that would fit on a T-shirt.
Asked whether they are recommending Vlad over Capistrano, they answered this:
RD: Absolutely. We were targeting 80% of the cap features in 20% of the code, so it seems reasonable for us to target 80% of the cap users. The ones with really esoteric setups probably have their cap-fu down so strong they don't want to move anyways.Asked whether there could be some cooperation or interaction between the Capistrano and Vlad projects, the Ruby Hit Squad seems positive:
WB: Absolutely. We want to accomodate most of Capistrano's users, and also the ones that can't make it work.
EH: We also want vlad to work for more than just deploying web sites. In the rapidly-approaching 1.1 you'll be able to skip including the default vlad recipes and use it as a general system administration tool.
WB: I would like to see a repository of system-specific commands for performing various tasks. Both tools could make use of something like that. It might be possible to move SCM support into a library that could be shared, as well. After conquest comes assimilation.What is your experience with Capistrano?
RD: It is certainly possible... I'm not really willing to speculate. I do agree with Wilson that there is probably a nice middle ground we can both benefit from.
What a cool name
Steven Ihde,Karan Parikh Mar 29, 2015