puppet-rvm icon indicating copy to clipboard operation
puppet-rvm copied to clipboard

A puppet module for installing and using RVM (Ruby Version Manager)

Results 37 puppet-rvm issues
Sort by recently updated
recently updated
newest added

passenger now installs mod_passenger.so to the buildout directory. This version should work for this, and also retain the old locations for older versions

This is very useful when install gems like buildr that requires access to the JAVA_HOME environment variable: ``` rvm_gem { "${ruby193}@buildr/buildr": ensure => '1.4.7', environment => "JAVA_HOME=/usr/lib/jvm/java-6-openjdk/", require => [Rvm_gemset["${ruby193}@buildr"],...

RVM's installer now supports the specification of a source repository for installation from non standard locations (i.e., internally hosted repositories).

As of Phusion Passenger version 4.0.7 the compiled mod_passenger.so module is located in a NEW directory. This small patch adds a different load path based on the new location while...

Previous behavior would match anything containing the name, rather than exactly matching the name. This causes problems when you have two gems that match. It will always reinstall the gem...

Updated URL to point to new location for accessing github user content directly. Added -L to follow 301/302 redirects in the future.

The install script for passenger >= expects the home variable to be set. Choosing /tmp since we use it from puppet. Error: ``` /usr/local/rvm/gems/ruby-1.9.3-p429/gems/passenger-4.0.5/lib/phusion_passenger/platform_info/ruby.rb:202:in `expand_path': non-absolute home (ArgumentError) ``` Also...

The old script location redirects to the new one, but curl doesn't follow redirects by default.

Ubuntu 12.04.3 LTS (Precise Pangolin) rvm 1.22.10 passenger-4.0.16