Setup rbenv ruby manager for systemwide use

Justin Downing



101,646 latest version

5.0 quality score

Version information

  • 2.5.0 (latest)
  • 2.4.0
  • 2.3.0
  • 2.2.0
  • 2.1.0
  • 2.0.0
  • 1.5.1
  • 1.5.0
  • 1.4.1
  • 1.4.0
  • 1.3.0
  • 1.2.1
  • 1.2.0
  • 1.1.0
  • 1.0.3
  • 1.0.2
  • 1.0.1
  • 1.0.0
  • 0.2.3
  • 0.2.2
  • 0.2.1
  • 0.2.0
  • 0.1.0
  • 0.0.4
  • 0.0.2
  • 0.0.1
released Aug 17th 2019
This version is compatible with:
  • Puppet Enterprise 2019.8.x, 2019.7.x, 2019.5.x, 2019.4.x, 2019.3.x, 2019.2.x, 2019.1.x, 2019.0.x, 2018.1.x, 2017.3.x, 2017.2.x, 2017.1.x, 2016.4.x
  • Puppet >=4.9.3 <7.0.0
  • RedHat

Start using this module


jdowning/rbenv — version 2.5.0 Aug 17th 2019


Build Status Puppet Forge


This Puppet module will install and manage rbenv. By default, it installs rbenv for systemwide use, rather than for a user or project. Additionally, you can install different versions of Ruby, rbenv plugins, and Ruby gems.


puppet module install --modulepath /path/to/puppet/modules jdowning-rbenv


To use this module, you must declare it in your manifest like so:

class { 'rbenv': }

If you wish to install rbenv somewhere other than the default (/usr/local/rbenv), you can do so by declaring the install_dir:

class { 'rbenv': install_dir => '/opt/rbenv' }

You can also ensure rbenv is kept up-to-date:

class { 'rbenv':
  install_dir => '/opt/rbenv'
  latest      => true

The class will merely setup rbenv on your host. If you wish to install rubies, plugins, or gems, you will have to add those declarations to your manifests as well.

Installing Ruby using ruby-build

Ruby requires additional packages to operate properly. Fortunately, this module will ensure these dependencies are met before installing Ruby. To install Ruby you will need the ruby-build plugin. Once installed, you can install most any Ruby. Additionally, you can set the Ruby to be the global interpreter.

rbenv::plugin { 'rbenv/ruby-build': }
rbenv::build { '2.0.0-p247': global => true }

Sometimes Ruby needs to be patched prior to being compiled. puppet-rbenv currently supports patching from a single file located either on the Puppet Master or the local filesystem. Therefore, the only accepted paths are those starting with puppet:/// or file:///.

rbenv::build { '2.0.0-p247': patch => 'puppet:///modules/rbenv/patch.patch' }
rbenv::build { '2.0.0-p247': patch => 'file:///path/to/patch.patch' }


Plugins can be installed from GitHub using the following definiton:

rbenv::plugin { 'github_user/github_repo': }

You can ensure a plugin is kept up-to-date. This is helpful for a plugin like ruby-build so that definitions are always available:

rbenv::plugin { 'rbenv/ruby-build': latest => true }


Gems can be installed too! You must specify the ruby_version you want to install for.

rbenv::gem { 'thor': ruby_version => '2.0.0-p247' }

Full Example


class { 'rbenv': }
rbenv::plugin { [ 'rbenv/rbenv-vars', 'rbenv/ruby-build' ]: }
rbenv::build { '2.0.0-p247': global => true }
rbenv::gem { 'thor': ruby_version => '2.0.0-p247' }


You can run specs in this module with rspec:

bundle install
bundle exec rake spec

Or with Docker:

docker build -t puppet-rbenv .


You can also test this module in a Vagrant box. There are two box definitons included in the Vagrant file for CentOS and Ubuntu testing. You will need to use librarian-puppet to setup dependencies:

bundle install
bundle exec librarian-puppet install

To test both boxes:

vagrant up

To test one distribution:

vagrant up [centos|ubuntu]