It's good enough for me. And that's very handy it is supported by various gems.
Example from this week: It's nice to have all you new gems from Gemfile checked and installed on deploy. Just do "require 'bundler/capistrano"' and you're done. Same with cron table update if you use "whenever" gem for that. "require 'whenever/capistrano'" and it'll run required tasks automatically. Also, I always use capistrano with capistrano-ext gem, which allows to have different configs for "cap staging deploy" and "cap production deploy". Pretty cool. Is there any reason to use something else? On Sun, Feb 20, 2011 at 9:50 PM, Scott Walter <[email protected]> wrote: > Hi, > > Its been a couple years since I've done any Rails development but have > decided to start on a project. Is Capistrano still the favorite tool > for deployment or is there another one that most people use these days? > > Thanks, Scott. > > -- > Posted via http://www.ruby-forum.com/. > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Talk" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/rubyonrails-talk?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.

