Rvm System-Wide Install Script Url Broken -- What Is Replacement

RVM system-wide install script url broken -- what is replacement?

Here is my fix to install the last working version before he major change:

bash <( curl -L https://github.com/wayneeseguin/rvm/raw/1.3.0/contrib/install-system-wide ) --version '1.3.0'

This is working for me now in production. Good luck!

UPDATE

Also, if you are using the chef cookbook from https://github.com/fnichol/chef-rvm or something similar, you can use the following options:

:rvm => {
  :system_installer_url => "https://github.com/wayneeseguin/rvm/raw/1.3.0/contrib/install-system-wide",
  :version => "1.3.0"
}

Installing Rubies in system wide RVM 1.5.2 install problem

It appears that the install scripts have been updated to correct this, so it doesn't appear to be an issue anymore.

With a system wide install of RVM, which user do you run bundle install as?

bundler's doc explicitly says don't do it as root:

http://gembundler.com/man/bundle-install.1.html

Quoted:

You should never use sudo bundle
install. This is because several other
steps in bundle install must be
performed as the current user:

1) Updating your Gemfile.lock

2) Updating
your vendor/cache, if necessary

3) Checking out private git repositories
using your user's SSH keys

Especially true with RVM:

http://rvm.beginrescueend.com/rubies/rubygems/

Quoted:

DO NOT use sudo...

to work with RVM gems. When you do
sudo you are running commands as root,
another user in another shell and
hence all of the setup that RVM has
done for you is ignored while the
command runs under sudo (such things
as GEM_HOME, etc...). So to reiterate,
as soon as you 'sudo' you are running
as the root system user which will
clear out your environment as well as
any files it creates are not able to
be modified by your user and will
result in strange things happening.
(You will start to think that someone
has a voodoo doll of your
application...)

With a system wide install of RVM, which user do you run bundle install as?

bundler's doc explicitly says don't do it as root:

http://gembundler.com/man/bundle-install.1.html

Quoted:

You should never use sudo bundle
install. This is because several other
steps in bundle install must be
performed as the current user:

1) Updating your Gemfile.lock

2) Updating
your vendor/cache, if necessary

3) Checking out private git repositories
using your user's SSH keys

Especially true with RVM:

http://rvm.beginrescueend.com/rubies/rubygems/

Quoted:

DO NOT use sudo...

to work with RVM gems. When you do
sudo you are running commands as root,
another user in another shell and
hence all of the setup that RVM has
done for you is ignored while the
command runs under sudo (such things
as GEM_HOME, etc...). So to reiterate,
as soon as you 'sudo' you are running
as the root system user which will
clear out your environment as well as
any files it creates are not able to
be modified by your user and will
result in strange things happening.
(You will start to think that someone
has a voodoo doll of your
application...)

rvm doesn't install in centos without root privileges

I was trying to install rvm in folder mounted with noexec option.

Mounting partition without this option works!

for compiled libraries, like libyaml, where does Ruby (or the RVM) search within the filesystem in order to load or resolve them?

Remove all rvm, ruby, libyaml, etc.

Than install rvm, and only use rvm to install libyaml and rubies.

(Also do note that Ruby can look for 32 bit libraries, so check if there is version for 32 bits, or if there is separate lib folder for 64bit libraries!)

PS Go check heroku for hosting your apps. Great for begginers as its free, and 5 min to set up (15 min from installing rails to rails autogenerated webpage on heroku!). And you do not need to change your configs, so deployment on your server will not be harder.

sudo gem install' or 'gem install' and gem locations

Contrary to all the other posts I suggest NOT using sudo when installing gems.

Instead I recommend you install RVM and start a happy life with portable gem homes and different version of Ruby all living under one roof.

For the uninitiated, from the documentation:

RVM is a command line tool which allows us to easily install, manage and work with multiple ruby environments and sets of gems.

The reason why installing gems with sudo is worse than just gem install is because it installs the gems for ALL USERS as root. This might be fine if you're the only person using the machine, but if you're not it can cause weirdness.

If you decide you want to blow away all your gems and start again it's much easier, and safer, to do so as a non-root user.

If you decide you want to use RVM then using sudo will cause all kinds of weirdness because each Ruby version you install through RVM has its own GEM_HOME.

Also, it's nice if you can make your development environment as close to your production environment as possible, and in production you'll most likely install gems as a non-root user.

Why is Ruby not available to me after compiling from source?

Is /opt/rubies/ruby-2.0.0-p247/bin in your $PATH? With a --prefix like that then make install will put all the binaries in $prefix/bin basically.

If you do

$ ls /opt/rubies/ruby-2.0.0-p247

You'll see all your binaries

---

Related Topics