I was having trouble installing rvm on WebFaction, so I tried just copying over the .rvm directory with my rubies and gems. This has mostly worked. rvm works, it’s referencing the correct ruby, and the correct gem. The problem it seems, is rvm is looking for an environment file in the wrong place. It’s trying to use:
/Users/jezen/.rvm/environments/ruby-2.0.0-p247
Whereas it should be using:
/home/rekyl/.rvm/environments/ruby-2.0.0-p247
Where can I set the correct path?
check /Users/jezen/.rvm/wrappers/ruby-2.0.0-p247/ruby but also /home/rekyl/.rvm/environments/ruby-2.0.0-p247 is relevant, make sure all environment variables point to proper path:
env | grep rvm
Related
Asking RVM to
rvm install ruby-1.9.3p551
fails because of error fetching the ruby interpreter. earlier errors state
The requested url does not exist(22): 'http://cache.ruby-lang.org/pub/ruby/./ruby-1.9.3p551.tar.bz2'
and two fallbacks fails as well...
Checking the URLs, they effectively do not exist.
http://cache.ruby-lang.org/pub/ruby/
has the list of rubies, and a proper path to download is
http://cache.ruby-lang.org/pub/ruby/ruby-1.9.3-p551.tar.bz2
why is that dot directory in the middle of an otherwise proper path and how can I get RVM to get the right path (or use the archive downloaded?
Try
rvm list known
to get the list of ruby versions.
I think that you can get this version by
rvm install ruby-1.9.3-p551
We are using RVM to manage rubies and gemsets for dozens of projects.
Sometimes I'll either edit the .ruby-version or .ruby-gemset file, or pull a newer version of those file(s) from our VCS, but of course RVM is unaware of these changes unless I tell it. And if the changes come from the VCS, even I may not be aware of them. So what's the best way to do this?
It would be nice to be able to automate the process, so that it is done automatically any time I fetch changes from the repository.
The only way I know of to get RVM to re-read these files is to cd to another directory, then return to the project directory. This is obviously simple, and easy, but it seems more than a little inelegant, and isn't self-documenting.
I'd expect there to be some command like rvm reload (which exists, but does something else) to re-read the project files, but I can't find anything of the sort.
I think I've found an answer, but as it is undocumented I don't know if it's really legit.
It seems that if you do:
$ rvm use .
It'll apparently (re)read the .ruby-version and .ruby-gemset files (not sure of .rvmrc files, since we don't use them). I discovered this by trying rvm use .ruby-version and rvm use .ruby-gemset, both of which seemed to cause RVM to read both 'dot' files.
This functionality is not currently (as of RVM 1.23.13) mentioned in the documentation (i.e. rvm help use).
Maybe it should be?
I use .rvmrc and I used to do
cd;cd -
but now I do
cd .
If I do
rvm use .
I get
Could not determine which Ruby to use; . should contain .rvmrc or .versions.conf or .ruby-version or .rbfu-version or .rbenv-version, or an appropriate line in Gemfile. ( see: 'rvm usage' )
which I don't really think is true (because I do have a .rvmrc file in .), or perhaps I just don't understand.
Edit:
I am using rvm 1.25.33
I didn't mean to come across as critical, just trying to add more info!
Is there a way to get rid of the warning, when I traverse into a folder having a .rvmrc file.
====================================================================================
= NOTICE =
====================================================================================
= RVM has encountered a new or modified .rvmrc file in the current directory =
= This is a shell script and therefore may contain any shell commands. =
= =
= Examine the contents of this file carefully to be sure the contents are =
= safe before trusting it! ( Choose v[iew] below to view the contents ) =
====================================================================================
Do you wish to trust this .rvmrc file? (/home/sam/myrailsapp/.rvmrc)
y[es], n[o], v[iew], c[ancel]> y
To switch from .rvmrc to .ruby-version + .ruby-gemset
rvm rvmrc to .ruby-version
There is a bug right now in RVM that keeps it asking you trusting .rvmrc.
Solution is simple - use .ruby-version instead:
1.9.3
or
1.9.3#gemset
Gemset will be created automatically for you.
.ruby-version is only for Ruby versions switching. If you need some scripting when switching Ruby, you still need .rvmrc.
According to the documentation:
To turn off the project specific rvmrc functionality in your $HOME/.rvmrc set:
rvm_project_rvmrc=0
I don't have a RVM instance to try it out, but I guess that's what you are looking for.
I'd also suggest to use rbenv instead of RVM, for the following reasons.
If RVM has been installed with sudo, you'll have to cd to the directory as root.
If you trust the .rvmrc or .ruby-env as root, the notice shouldn't come back.
I have a an app that runs and is installed on JRuby in production. The same app can run in Ruby 1.8.7 as well in development. How can I use RVM to switch between these rubie?
I am looking for a .rvmrc-like solution so that I can say
rvm use .rvmrc_ruby
or
rvm use .rvmrc_jruby
to switch between Ruby versions. I usually need to do this to test the same app on both Ruby and JRuby.
I would like a solution where I can check-in such settings to Git and run these things without having to type the Ruby versions or gemset names everytime I need to switch.
generate those two files and in .rvmrc write:
source ./.rvmrc_${TEST_WITH:-jruby}
then you can write in your shell:
export TEST_WITH=ruby
cd .
and restore with:
unset TEST_WITH
cd .
This seems silly.
First, why are you even bothering to run a different Ruby in development? If this is for the occasional test run to ensure compatibility across different Rubies, then okay, but then…
Second, all you probably have in your .rvmrc is rvm use 1.8.7 or rvm use jruby—that is all that happens when your .rvmrc file runs. What's so bad about just actually typing that out into the terminal? It's actually less characters than the example commands you gave, and you get tab-completion too. If you need consistency across shells and actually have to have the .rvmrc reflect the current Ruby you want, then just change the file. Or, if you really must, write a simple script to do it for you (say it's called changervmrc.sh):
#!/bin/bash
echo "rvm use $1" > .rvmrc
and invoke with ./changervmrc.sh jruby. You could adapt this to include switching to a specific gemset if needed.
I come in peace (re: rbenv) but I am super frustrated with rvm & .rvmrc. I keep on running into issues where I cd into my project folder only to find that my ruby & gemset environment has not been set correctly. So can someone once and for all tell me how to create a proper .rvmrc for my project.
I have tried both ways that I know of:
creating a .rvmrc and putting 'rvm use 1.9.2#GEMSET' in there (this works sometimes and sometimes not)
using the rvm --create --rvmrc 1.9.2#GEMSET command line tool which creates a more ellaborate .rvmrc but cd'ing into my project folder is still not giving me the desired result.
This problem is erratic. I will say that I am working on two different machines and syncing my project folder via Dropbox. So could this be a problem where rvm cannot verify the folder and therefore ignores the .rvmrc?
Any help will be greatly appreciated.
Every time you enter a project directory after changing its .rvmrc file, rvm will prompt you for accepting or not the new file. If you want to change your decision afterwards, you should use rvm rvmrc command:
rvm rvmrc {trust,untrust,trusted,load,reset}
You may need to set
rvm_project_rvmrc=1
in your shell config before the rvm scripts are sourced, e.g.:
rvm_project_rvmrc=1
[[ -s "$HOME/.rvm/scripts/rvm" ]] && source "$HOME/.rvm/scripts/rvm"