Lee makes a good point it was a knee-jerk answer on my part. Why aren't you doing 'bundle install --deployment' which totally avoids the issue.
Bundler comes with canned capistrano support if you require it in your deploy.rb. On Aug 2, 2011, at 10:07 AM, Lee Hambley <[email protected]> wrote: > Using `sudo` to install gems is a bad idea, because ubuntu is "broken" out of > the box, you should fix your system Ruby installation; it's broken for a > reason; and you should never run production applications on your host > machine's distributed Ruby. > > Ubuntu don't ship Ruby as a convenience for users, but as a requirement for > some of their internal script, installing Gems into the Ubuntu core paths > *can* break your OS… that's why RBV and /usr/local exist. > > Donovan's solution will work, but you shouldn't do it. If you don't know why > you shouldn't do it, ask a sysadmin. (and then, do whatever works for you, > but be certain to understand the *potential* problems you will introduce if > you start using sudo to install Ruby Gems with) > -- > * 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
