Thanks for that tip, mate. Am I correct in assuming that it's safe to tell Bundler not to actually require Capistrano when booting? IE: gem 'capistrano', :require => nil
Cheers, Nick On Friday, 11 May 2012 11:35:03 UTC-4, dbray wrote: > > It's fine in the development group and it should be present in the Gemfile > > I make a habit of always doing > > bundle install --binstubs > > On a new project so I can do > > bin/cap .... > > Instead of > > bundle exec cap ... > > On Friday, 11 May 2012 11:35:03 UTC-4, dbray wrote: > > It's fine in the development group and it should be present in the Gemfile > > I make a habit of always doing > > bundle install --binstubs > > On a new project so I can do > > bin/cap .... > > Instead of > > bundle exec cap ... > > On May 11, 2012, at 8:24 AM, Nick Hoffman <[email protected]> wrote: > > Hi guys. Is it necessary to put Capistrano in a Rails app's Gemfile, or at > least, in the "development" group in the Gemfile? > > If not, are there any benefits to doing so? > > Thanks, > Nick > > -- > * You received this message because you are subscribed to the Google > Groups "Capistrano" 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/capistrano?hl=en > > -- * You received this message because you are subscribed to the Google Groups "Capistrano" 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/capistrano?hl=en
