Manage development runtimes with rvs

rvs runtime can install and select Python, Node.js, and Java versions. These tools are optional and work independently of your Ravenstash repositories.

rvs checks downloads before installing them. Node.js installation requires gpgv from GnuPG. On Alpine, use Node.js from the operating system or another version manager because the required official downloads are not available.

Note

Runtime management is optional. You can use rvs sign-in and package commands with compatible tools installed by your operating system or another version manager.

Install runtimes

rvs runtime install python 3.14
rvs runtime install node 22
rvs runtime install java 21

List installed versions and locate one executable:

rvs runtime list
rvs runtime which python 3.14

Use --force with runtime install only when you intentionally want to remove and download the matching installation again.

Enable runtime shims

Print the environment changes for the current shell:

rvs runtime env

Or add the shim initialization to a supported shell startup file:

rvs runtime setup-shell

The command auto-detects Bash, Zsh, or Fish. Select one explicitly with --shell bash, --shell zsh, or --shell fish.

Review shell-startup changes before propagating them across managed developer machines.

Pin a project version

From a project directory:

rvs runtime use python 3.14
rvs runtime use node 22
rvs runtime use java 21

These commands write the conventional project selection files .python-version, .node-version, and .java-version. Commit them only when your team intends to share those runtime requirements.

Diagnose and remove runtimes

rvs runtime doctor
rvs runtime uninstall node 22

doctor is the first check when a command uses the wrong version. Removing a runtime does not edit project files that still refer to it.