Skip to content
Commits on Jan 15, 2015
  1. @lesniakania
Commits on Dec 19, 2014
  1. @lukeasrodgers

    Checking for gpg2 requires that we also *actually use* that command.

    lukeasrodgers committed
    Defaulting to gpg2, for parity with rvm.
  2. @lukeasrodgers

    Check for presence of gpg2 as well as gpg.

    lukeasrodgers committed
    Apparently some servers may have the former instead of the latter.
Commits on Dec 15, 2014
  1. @lukeasrodgers

    Use GPG for rvm verification.

    lukeasrodgers committed
    rvm will fail to install if GPG is present on the system, but the key
    for rvm is not found.
    This behaviour will be skipped if the `gpg_key` node is an empty string.
    Fixes #278
Commits on Sep 9, 2013
  1. @fnichol

    Refactor RVM installation code into rvm_installation resource.

    fnichol committed
    This is a nontrivial update and not 100% backwards compatible.
Commits on Jan 25, 2013
  1. @fnichol

    Handle rvm install flags with branch=stable & version=x.y.z.

    fnichol committed
    The readme explains that to use a tagged version that you must set the
    branch value to "none" which is overly surprising.
    The ultimate solution is cover the method responsible
    (#build_script_flags) with unit tests to catch all possible
    combinations. Unfortunetly the branch and version flags can interfere
    with each other making any solution here subpar.
    Closes #152
Commits on Aug 10, 2011
  1. @fnichol

    Major refactoring of recipes which will result in a minor version bump.

    fnichol committed
    There are now 2 main modes in which to use RVM: isolated as a user or
    * recipe[rvm] - pulls in the RVM gem and initializes Chef to use the
      LWRPs which is a breaking change to previous behavior. Use this recipe
      if you only want access to the LWRPs provided.
    * recipe[rvm::system_install] - only installs RVM framework system-wide.
      Use this recipe by itself if you want RVM installed but will handle
      rubies yourself (by hand, with the LWRPs, etc.)
    * recipe[rvm::system] - installs RVM system-wide and installs
      rubies, gems, etc. Use this recipe to get the same functionality
      previously availble by including recipe[rvm].
    * recipe[rvm:user_install] - installs the RVM framwork for one or more
      isolated users. Use this recipe if you want to handle rubies yourself.
    * recipe[rvm::user] - installs RVM for one or more isolated users and
      installs rubies, gems, etc. This is equivalent to recipe[rvm::system],
      but for user installs.
Something went wrong with that request. Please try again.