You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, we only use the --deployment flag when calling bundler for a non-staging site. This means that for staging sites, gems are installed in the system path. For avoiding our own server management headaches, we should always install the gems in a path local to the application. Additionally, I suspect this might also resolve #611, as it is the reason why bundler is using sudo to install rake.
Note: this needs to work for capistrano-based deploys.
The text was updated successfully, but these errors were encountered:
At the moment, we only use the --deployment flag when calling bundler for a non-staging site. This means that for staging sites, gems are installed in the system path. For avoiding our own server management headaches, we should always install the gems in a path local to the application. Additionally, I suspect this might also resolve #611, as it is the reason why bundler is using sudo to install rake.
Note: this needs to work for capistrano-based deploys.
The text was updated successfully, but these errors were encountered: