Questions[rvm](server)

I have a puppet setup containing a puppet master and couple of nodes - this works as intended.

However - on the latest node I am working on I need to install rvm/ruby+nginx/passenger. This is done using these puppet modules

maestrodev-rvm (v1.13.1) puppet-nginx (v0.6.0)

All of this is installed and working - I can do bundle install and confirm this is installed into the right gemset and if I go to a different folder i can confirm gem list is not picking up gems for this gemset.

Accessing my application also works and yields the expected results.

So far so good.. the problems starts next time puppet runs - this causes all of my gems with native extensions to break. I'm getting the error:

Message from application: incompatible library version - /usr/local/rvm/gems/ruby-2.3.1@robot/gems/http_parser.rb-0.6.0/lib/ruby_http_parser.so (LoadError)

When comparing the content of the file before/after puppet run (using md5sum) I'm getting different checksums.

It seems like I am getting some unexpected output when running

/opt/puppetlabs/puppet/bin/gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 2.2.5
  - RUBY VERSION: 2.1.9 (2016-03-30 patchlevel 490) [x86_64-linux]
  - INSTALLATION DIRECTORY: /usr/local/rvm/gems/ruby-2.3.1
  - RUBY EXECUTABLE: /opt/puppetlabs/puppet/bin/ruby
  - EXECUTABLE DIRECTORY: /usr/local/rvm/gems/ruby-2.3.1/bin
  - SPEC CACHE DIRECTORY: /root/.gem/specs
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86_64-linux
  - GEM PATHS:
     - /usr/local/rvm/gems/ruby-2.3.1
     - /usr/local/rvm/gems/ruby-2.3.1@global
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - https://rubygems.org/
  - SHELL PATH:
     - /usr/local/rvm/gems/ruby-2.3.1/bin
     - /usr/local/rvm/gems/ruby-2.3.1@global/bin
     - /usr/local/rvm/rubies/ruby-2.3.1/bin
     - /usr/local/sbin
     - /usr/local/bin
     - /usr/sbin
     - /usr/bin
     - /sbin
     - /bin
     - /opt/puppetlabs/bin
     - /usr/local/rvm/bin

How come it be the GEM PATHS are pointing to the ruby-2.3.1? How can I control this value when using the ruby bundled with puppet? I was only able to find the configuration to change gem path in the puppetserver documentation.

I'm working on deploying my first rails app to my mediatemple(dv) and i'm first trying to install RVM using this command:

bash -s stable < <(curl -s https://raw.github.com/wayneeseguin/rvm/master/binscripts/rvm-installer)

and I get the following error:

curl: (60) SSL certificate problem, verify that the CA cert is OK. Details:
error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
More details here: http://curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default, using a "bundle"
 of Certificate Authority (CA) public keys (CA certs). The default
 bundle is named curl-ca-bundle.crt; you can specify an alternate file
 using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
 the bundle, the certificate verification probably failed due to a
 problem with the certificate (it might be expired, or the name might
 not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
 the -k (or --insecure) option.

Could not download 'https://github.com/wayneeseguin/rvm/tarball/stable'.
  Make sure your certificates are up to date as described above.
  To continue in insecure mode run 'echo insecure >> ~/.curlrc'.

It looks like I should be able to specify -k/--insecure to skip the certificate check, but how can I do that? I'm kind of a linux rookie.

in a system wide RVM .... heres my /etc/gemrc

---
gem:--no-ri --no-rdoc

heres the system gem env

 GEM PATHS:
     - /usr/lib/ruby/gems/1.9.1
     - /home/${USER}/.gem/ruby/1.9.1
    GEM CONFIGURATION:
         - :update_sources => true
         - :verbose => true
         - :benchmark => false
         - :backtrace => false
         - :bulk_threshold => 1000
         - "gem" => "--no-ri --no-rdoc"

and heres the one in rvm

GEM PATHS:
 - /usr/local/rvm/gems/ruby-1.9.2-p180
 - /usr/local/rvm/gems/ruby-1.9.2-p180@global
GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000

and rvm @global

    GEM PATHS:
     - /usr/local/rvm/gems/ruby-1.9.2-p180
     - /usr/local/rvm/gems/ruby-1.9.2-p180@global
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000

why is it not picking up the gemrc file?

We are using RVM for managing Ruby installations and environments.

Usually we are using this .rvmrc script:

#!/bin/bash
if [ ! -e '.version' ]; then
  VERSION=`pwd | sed 's/[a-z/-]//g'`
  echo $VERSION > .version
  rvm gemset create $VERSION
fi
VERSION=`cat .version`
rvm use 1.9.2@$VERSION

This script forces RVM to create new gem environment for each our project/version.

But each time we was deploying new version RVM asks us to confirm new .rvmrc file.

When we cd to this directory first time, we are getting something like:

  ===============================================================
  = NOTICE:                                                     =
  ===============================================================
  = RVM has encountered a not yet trusted .rvmrc file in the    =
  = current working directory which may contain nasty code.     =
  =                                                             =
  = Examine the contents of this file to be sure the contents   =
  = are good before trusting it!                                =
  =                                                             =
  = Press 'q' to exit the reader when finished reading the file =
  ===============================================================

  (press enter to continue when ready)

This is not as bad for development environments, but with auto deploy it require to manually confirm each new version on each server.

Is it possible to skip this confirmation?

I'm using EC2 and sometimes launch servers that I want to use only for a short time. Usually I want to install some version or versions of Ruby on them, and for this RVM is very convenient -- if it wasn't for the fact that it takes forever to compile Ruby. It's really boring to have to wait almost half an hour just for Ruby to compile when the rest of the server setup is done in minutes. It completely kills the cloud computing experience.

Is there a way to get the convenience of RVM without the inconvenience of compiling each Ruby version for every new server I launch? Can I precompile a Ruby version and keep it somewhere accessible, and then have RVM use that instead of compiling it from source? Can I simply archive some directory under the RVM root dir after I've installed a Ruby version, save it somewhere and then extract it in the right place on the next server I launch? In that case, which files and directories do I need to keep?

I want to use RVM not only to be able to switch between Ruby versions, but also because it allows me to keep separate gemsets for different applications, so not using RVM would be very inconvenient.

All servers have the same OS and architecture, Ubuntu 10.04, 32 bit.