Setting up the command_map works wonderfully. Quite an elegant way of handling this.
Should this be done automatically in the capistrano/bundler gem? (I believe something similar was done in the old gem) Thanks, David On Thursday, November 14, 2013 4:04:50 AM UTC-6, Andrei Varanovich wrote: > > try setting this in your deploy.rb > > SSHKit.config.command_map[:rake] = "bundle exec rake" > > > On Tuesday, November 12, 2013 7:29:18 PM UTC+1, [email protected]: >> >> I'm unable to run the correct rake version because calls to rake don't >> take into account I'm using bundler. >> >> I've included: >> require 'capistrano/bundler' >> along with: >> require 'capistrano/rails/assets' >> require 'capistrano/rails/migrations' >> >> Deploying works fine until it comes time to run the assets:precompile >> task. The command that is executed is: >> >> RAILS_ENV=staging /usr/bin/env rake assets:precompile >> >> Instead of "rake" it should be "bundle exec rake" or "bin/rake" because >> I'm using bundler. >> >> I've tried setting the value of :rake, by adding: >> set :rake, 'bundle exec rake' >> to my deploy.rb file. However, it doesn't make any difference. >> >> I'm not sure if this is an issue with Capistrano, or more likely with the >> Capistrano bundler support? >> >> Any thoughts on how to fix this? >> >> Thanks, >> >> David >> >> -- -- * 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
