CODEWITHSUNDEEP
ruby-on-railsrubygemsbundler
nfm
nfm

Reputation: 20677

Can't get bundle exec to work in production

I've installed my gems in production with:

cd /app/releases/current && bundle install --gemfile /app/releases/current/Gemfile --path /app/shared/bundle --deployment --quiet --without development test

I can't bundle exec any of my gems (except rake and gem):

$ bundle exec whenever
bundler: command not found: whenever
Install missing gem executables with `bundle install`

The gems are correctly installed in /app/shared/bundle:

$ cd /app/shared
$ find . -name whenever
./bundle/ruby/1.9.1/gems/whenever-0.6.8/bin/whenever
./bundle/ruby/1.9.1/gems/whenever-0.6.8/lib/whenever

My (generated) bundle config (in /app/current/.bundle/config) is:

---
BUNDLE_FROZEN: "1"
BUNDLE_PATH: /app/shared/bundle
BUNDLE_DISABLE_SHARED_GEMS: "1"
BUNDLE_WITHOUT: development:test

I'm running ruby 1.9.2p290, manually installed to /usr/local/bin.

Do I have to bundle install my gems with the --binstubs option? Why wouldn't bundle exec be searching the stored BUNDLE_PATH?

Upvotes: 16

Views: 10344

Answers (7)

nruth
nruth

Reputation: 1068

Using the brightbox deployment gem, which handles bundler etc for me (by magic, in some other recipes) I found this works:

Replace

require "whenever/capistrano"

with the contents of https://github.com/javan/whenever/blob/master/lib/whenever/capistrano/v2/hooks.rb then modify it to load after bundler:install finishes (you may or may not have that task, I don't know if it's standard)

# require "whenever/capistrano"
# hacked whenever/lib/whenever/capistrano/v2/hooks.rb below to work with brightbox bundler installation

require "whenever/capistrano/v2/recipes"

# Write the new cron jobs near the end.
after "bundler:install", "whenever:update_crontab"
# If anything goes wrong, undo.
after "deploy:rollback", "whenever:update_crontab"

Upvotes: 0

wickning1
wickning1

Reputation: 91

I had this problem and had the requires in the correct order, i.e.

require 'rvm/capistrano'
require 'bundler/capistrano'
require 'whenever/capistrano'

It still wanted to run the crontab update before bundle:install. The solution was to update my local bundler with

gem update bundler

After that it started working again. Not sure exactly what changed between versions that broke all of this.

Upvotes: 4

aproctor
aproctor

Reputation: 93

Check where your bundle:install is being set, and try moving it above require 'whenever/capistrano' in your deploy.rb file.

It seems like this was triggered when I did a bundle update that increased the whenever gem version in my Gemfile.lock.

It looks like whenever tries to run it's chrontab update before my deploy file runs bundle:install

from https://github.com/javan/whenever/blob/master/lib/whenever/capistrano.rb

before "deploy:finalize_update", "whenever:update_crontab"

And my deploy.rb had

after 'deploy:finalize_update', 'bundle:install'

Like everyone else in this thread, I tried a few things and I'm not sure this is what fixed it for me, but changing bundle install to before deploy:finalize_update, and also setting it as "before" above requiring 'whenever/capistrano' seems like it's the likely fix in my scenario.

Upvotes: 1

Jan
Jan

Reputation: 3124

Probably different issues cause the same error message. For me, I had to update capistrano gem after having updated whenever gem to get roles support. bundle exec whenever had worked prior to my upgrade of whenever.

Upvotes: 0

Ccastillop
Ccastillop

Reputation: 791

Using Capistrano and Rails and using deploy.rb as deployer file.

I realized that changing the order where appears require "whenever/capistrano" really matters. I put that at almost the last line:

In deploy.rb:

#first lines:
set :rvm_ruby_string, "1.9.3"
set :rvm_type, :user
set :whenever_command, "bundle exec whenever"

# others...

# last lines
require 'rvm/capistrano'
require 'bundler/capistrano'
require "whenever/capistrano"

after "deploy:update_code", "customs:config"
after "deploy:create_symlink","deploy:create_symlink"
after "deploy", "deploy:cleanup"

load 'deploy/assets'
# end

Upvotes: 8

nfm
nfm

Reputation: 20677

I changed the --path from /app/shared/bundle to vendor/bundle, which made it work.

This seemed wrong to me, so I removed /app/shared/bundle and vendor/bundle, and ran bundle install again to /app/shared/bundle.

This clean bundle install fixed the problem. I have no idea why!

If anyone has an explanation for this, I'd love to mark you as the accepted answer. But this fixed the problem for me.

Upvotes: 0

lidaobing
lidaobing

Reputation: 1075

I think when whenever gem is not in your Gemfile, or it's in the test or development section of your Gemfile

Upvotes: 0

Related Questions