See Authoring plugins for instructions on how to write new commands for rbenv or hook into its functionality.
A plugin can be installed by dropping it in as a sub-directory of
$RBENV_ROOT/plugins, or it can be located elsewhere on the system as long as
rbenv-* executables are placed in the
$PATH and hooks are installed
accordingly somewhere in
This list is edited by rbenv maintainers.
rbenv rehashevery time you install a new gem
~/.gemor a custom
There is rbenv-bundler which
adjusts rbenv's shims and
rbenv which command with respect to the current
project's bundle. However,
its usage is not recommended
because of poor performance and being bug-ridden.
If you want to free yourself from having to always write
bundle exec <command>
in a project, you can generate Bundler's binstubs:
bundle install --binstubs
Now you can run
bin/rake instead of
bundle exec rake.
If you want to be able to just type
rake, you have two options from here:
$PATH. See Understanding binstubs for more info.
rbenv rehashfrom your project.
Please add new plugins here. They might get promoted to the above list by rbenv maintainers.
rbenv install(externalised ruby-build hooks)
bundle execwhen invoked from a bundler-managed directory
gem cleanfor rbenv
gem update --systemon
rbenv gitcommand to run
gitin directories of rbenv and all installed plugins
Mygemfileas bundler gemfile if it exists
$PATH(likely of interest to plugin writers)
.ruby-versionfile inside the root of the installation directory