is not checked out... bundle install does NOT fix help!

Question

https://github.com/intridea/omniauth.git (at master) is not checked out. Please run `bundle install` (Bundler::GitError)

So what do I do? bundle install works on development, but when I push and deploy to my production server. I get this error, even after running bundle install on my production server.

Solution 1

You're probably running Passenger. This is the issue with some solutions - http://code.google.com/p/phusion-passenger/issues/detail?id=505

Try running bundle install --deployment

Solution 2

This error can be related to the spring gem. Regenerating spring binstubs worked for me.

bundle exec spring binstub --all

https://github.com/rails/spring/issues/387

Solution 3

for the guys that stuck with "bundle & git repo " problems.

1. $ bundle pack
2. $ bundle install --path vendor/cache

more details, please refer to https://stackoverflow.com/a/5268534/445908

Solution 4

For me it was just a matter of adding this to gemfile:

source 'http://gems.github.com'

Solution 5

When your computer never restarts, Spring might be the problem. Spring was running for 350 hours and caused caching the outdated TEST environment. I had this problem in my cucumber test environment in Rubymine. Strange this was that from (mac) the command prompt there was no problem.

spring status
spring stop

and voila! It all worked again.

View more solutions

Comments

[fivetwentysix]

Just a note, got a depreciation message running 3.0.9 stating that we should use bundle install path deployment.

[Greg Funtusov]

That masks the problem more than solves it – --deployment mode is not intended for development and poses problems with each bundle.

[SnakeWasTheNameTheyGaveMe]

Also adding to the discussion: I was having the same problems, so I tried explicitly setting the user in nginx.conf to the user for which RVM was installed and it worked. So before it was commented out: #user nobody;, now it's: user jake.

[Hass]

I had the same problem with Pow and this fixed it too.

[ethree]

+1. Saved my day a few times. Interesting that I have to install bundles with --no-deployment, and then again with --deployment for Redmine.

[Dennis]

Note that this solution won't work now because GitHub no longer builds gems. See webcache.googleusercontent.com/…

[Dennis]

"In deployment mode, Bundler will ´roll-out´ the bundle for production use." This vendors (copies) the gems into your development app, bloating the app's code. There must be a better way to solve the issue?

[Dennis]

Regarding my previous comment: Try removing Gemfile.lock and .bundle/config from your project and running bundle install. (Note that the lack of a Gemfile.lock may cause some gems to update when you run bundle install.) It fixed the issue for me. Worth a try before you enable deployment mode in development or test environments.

[Janosch]

This can also happen if you change your repo urls from git:// to https://. spring stop a.k.a. "have you tried turning it off and on again?" is the only (!) thing that will work in that case.

[Adrian Teh]

In case you guys need it later, this is how you revert it: bundle install --no-deployment

[paascal]

This was the solution to my problem after upgrading too. Upvoted :)

[flacko]

That fixed it for me as well. Much appreciated!

[Sylhare]

Bundle is recommending to use bundle config set --local path 'vendor/bundle' instead as --path is deprecated.

[Sylhare]

The --deployment in now deprecated, it is now best to use bundle config set --local deployment 'true'