rbenv/rbenv
Rbenv
rbenv is a Ruby version manager and shell environment manager designed to install, switch between, and manage multiple versions of the Ruby programming language. It functions as a project runtime isolator and an extensible versioning framework that ensures the correct Ruby binaries are executed based on the current context.
The system uses a shim-based command interception model to resolve the active version before delegating execution to the binary. It allows for locking specific Ruby versions and environment variables to individual directories, ensuring project environment isolation. The architecture is designed for extensibility, allowing users to add custom commands and hooks through a plugin system.
The tool covers a broad range of capabilities including version management, toolchain configuration, and the management of environment variables. It provides mechanisms to automate library setup and isolate dependencies across different installations.
Features
- Version Managers - Provides a comprehensive system for installing, switching, and managing multiple Ruby runtime versions.
- Ruby Version Managers - Provides a comprehensive system for installing and managing different versions of the Ruby programming language.
- Command Interception Shims - Uses proxy mechanisms to dynamically resolve and route command execution to the correct Ruby binary.
- Runtime Version Switching - Enables switching between different Ruby versions based on global defaults, project files, or shell sessions.
- Shell Environment Managers - Modifies terminal sessions by injecting environment variables and updating paths to ensure correct binary execution.
- Per-Project Runtime Assignments - Binds a specific Ruby runtime version to a directory to ensure project-specific environment consistency.
- Shim-Based Command Interception - Implements a shim-based interception model to execute the correct Ruby binaries and gems without manual path configuration.
- Environment Isolation - Isolates language runtimes by assigning specific Ruby versions to directories to ensure consistent behavior across projects.
- Multi-Version Installations - Provides the capability to download and install multiple specific versions of the Ruby runtime.
- Directory-Based Version Resolution - Determines the active Ruby version by searching for configuration files in the current and parent directories.
- Isolated Runtime Directories - Installs separate language versions into distinct folders to prevent binary conflicts.
- Shim Regeneration - Rebuilds proxy executables to ensure the command line interface maps to the latest installed binaries.
- Command Line Extensions - Provides a framework for defining custom commands and plugins to extend the version manager's functionality.
- Dependency Isolation Tools - Provides utilities for configuring custom paths to isolate language-specific dependencies (gems) per project.
- Environment Variable Management - Manages host-level environment variables for both global and project-specific runtime configurations.
- Environment Variable Configurations - Provides mechanisms to inject runtime settings and configuration parameters via project-specific environment variable files.
- Shell Environment Injections - Injects logic into the shell session to update environment variables and modify the command search path dynamically.
- Hook-Based Extension Frameworks - Uses a hook-based architecture to allow plugins to add custom commands and extend environment management.
- Plugin Extenders - Allows loading custom external libraries at runtime to augment core version management functionality.
- Plugin Managers - Facilitates the discovery, installation, and management of third-party extensions to add new functionality.
- Tooling Plugin Systems - Implements an architecture for adding custom tools and commands via external plugin loading.
- Command Line Utilities - Version management for Ruby environments.
Star history
How this analysis was created: This summary and feature list were written by an AI model that read the project's README and public documentation pages. Each feature links to the documentation it came from; stars, license and language come straight from the GitHub API. The model does not read the source code, and the analysis is refreshed when the project is re-analysed. Learn more on our About page.
