I removed RBENV and switched to RVM.
Now when i try to deploy with capistrano, or even try to just run "cap" i get:
/Users/me/.rbenv/shims/cap: No such file or directory
It's obviously still looking for the rbenv shim, but how do i get capistrano working on RVM?
I've tried removing and re-installing the gem, but that did not work...
make sure $PATH is clear from /Users/me/.rbenv, then you can call hash -r to invalidate PATH cache.
also make sure you install gems again, both rbenv and rvm use custom paths for installing gems - so it's required to install gems again.
Related
If I run rvm install 2.0.0, it goes through the normal steps (downloading, extracting, configuring, compiling, installing), but ends by simply saying:
ruby-2.0.0-p0 is not installed.
To install do: 'rvm install ruby-2.0.0-p0'
I've tried the following:
rvm remove 2.0.0
rvm get head
rvm requirements
rvm install ruby-2.0.0
I keep getting the same result: no error, it just "is not installed." Anybody know what's wrong?
I had the same issue and managed to work it out.
When I did an echo $CC it came up with /usr/bin/gcc-4.2. So I did an export CC=clang, then rvm reinstall 2.0.0 and it worked.
Hope that helps.
rvm get ruby here => http://ftp.ruby-lang.org/pub/ruby/
Maybe you should get the right ruby version to install. Something like ruby-2.0.0-rc1 or ruby-2.0.0-rc2 is the latest ruby version.
if you are getting this message when you open a Rails folder, then you need to remove the .ruby-version file which is inside the folder and re-run a bundle install:
rm .ruby-version
bundle install
After I installed a version of ruby with rvm, I noticed that some minor configuration issue on installation process. So I wanted to try to install with another configuration options, but I don't want to spoil the installed ruby at all.
So I just to attempt to backup the installed ruby before rvm reinstall.
(cd .rvm/rubies && mv ruby-1.9.3-p194 ruby-1.9.3-p194.org)
In my case, reinstallation fixed the issue, I didn't rollback ruby. So, I don't know this can work.
Are there any clean or correct way? Just for future references.
you can install named rubies:
rvm install 1.9.3-test1 [options]
and after it worked set it as default:
rvm use 1.9.3-test1 --default
or reinstall the original 1.9.3, named rubies are useful especially for testing compilation flags or patched rubies:
rvm install 1.9.3-performance --patch falcon
You can also have different gemsets with the same version using
rvm create gemset projectname
I have deployed my application on linux server with passenger and apache, I have done bundle install run successfully still i get
( git://github.com/ryanb/nested_form.git (at master) is not checked out. Please run bundle install (Bundler::GitError) ) error while i try to run my application
FYI, i am using rails 3.2.3 and ruby 1.9.3
This works fine on my development machine
Any Idea ?
I have currently solved the issue by running below
bundle pack
bundle install --path vendor/cache
This solves my problem, but it stores whole gems in the vendor directory
But still if anybody have better solution then please let me know
I had the same problem, I always installed my gems as system-wide gems (including the ones from github).
$ sudo bundle install
When I ran rails, I got the same error:
$ rails s
http://github.com/Sija/garb.git (at master) is not checked out. Please run `bundle install`
So when I ran:
$ bundle install
This installed the gems from github locally, but otherwise used all the other system-wide gems.
Then when I ran rails again, it worked.
Are you running bundle install as root? If yes, try running bundle install without "sudo", anyway this seems to be a permissions problem (as Google suggests [google => (at master) is not checked out. Please run bundle install (Bundler::GitError)])1
Not sure what's going on here, but in my Rails 3 application, I type bundle install and at the end if says Your bundle is complete! It was installed into ./runner.
Weird because I have no idea where runner is coming from!
If I recall correctly, if you run something like bundle install ./runner it will remember the path ./runner. bundle install --system should fix it. i think.
See the manpage:
--path=<path>
The location to install the gems in the bundle to.
This defaults to the gem home, which is the location
that gem install installs gems to. This means that, by
default, gems installed without a --path setting will
show up in gem list. This setting is a remembered option.
--system
Installs the gems in the bundle to the system location.
This overrides any previous remembered use of --path.
I'm running a Rails 3.0.3 app using RVM (Ruby 1.8.7). When I run bundle install all the gems install and then I get this message Your bundle is complete! It was installed into ./rails. But the app isn't recognizing/see those gems. Not sure what I've done wrong that it's doing this. Let me know if you need any other information.
I bet you accidentally ran bundle install rails at one point, which configured your bundler to install your gems into the ./rails directory.
To reset that, remove the ./.bundle directory (or remove the BUNDLE_PATH line from ./.bundle/config). Then bundle install will put them in the right spot.