rbenv-installer VS asdf

curl -fsSL https://github.com/rbenv/rbenv-installer/raw/HEAD/bin/rbenv-installer | bash

$ git clone https://github.com/rbenv/rbenv.git ~/.rbenv $ echo 'eval "$(~/.rbenv/bin/rbenv init - bash)"' >> ~/.bashrc $ exec $SHELL $ git clone https://github.com/rbenv/ruby-build.git "$(rbenv root)"/plugins/ruby-build $ git clone https://github.com/rbenv/rbenv-vars.git "$(rbenv root)"/plugins/rbenv-vars $ rbenv install 3.2.0 $ rbenv global 3.2.0 # Test complete install with rbenv-doctor $ curl -fsSL https://github.com/rbenv/rbenv-installer/raw/main/bin/rbenv-doctor | bash $ ruby -v # Shows ruby version number if correctly installed $ gem install bundler # You might be prompted to update some gems, see command below $ gem update --system 3.4.6 # Check if this is recommended after bundler installation $ bundle -v # Shows bundler version number if correctly installed

# Install dependencies required to install Ruby sudo apt install git curl libssl-dev libreadline-dev zlib1g-dev autoconf bison build-essential libyaml-dev libreadline-dev libncurses5-dev libffi-dev libgdbm-dev # Install rbenv via GitHub curl -fsSL https://github.com/rbenv/rbenv-installer/raw/HEAD/bin/rbenv-installer | bash # Add ~/.rbenv/bin to $PATH echo 'export PATH="$HOME/.rbenv/bin:$PATH"' >> ~/.bashrc # Load rbenv automatically echo 'eval "$(rbenv init -)"' >> ~/.bashrc # Apply changes to current Shell sessions source ~/.bashrc

$ sudo apt update; sudo apt upgrade -y $ sudo apt install rbenv $ rbenv init # Follow instructions: append 'eval "$(rbenv init -)"' to ~/.bashrc $ source ~/.bashrc # or disconnect and reconnect $ mkdir -p "$(rbenv root)"/plugins $ sudo apt install git $ git clone https://github.com/rbenv/ruby-build.git "$(rbenv root)"/plugins/ruby-build $ git clone https://github.com/rbenv/rbenv-vars.git "$(rbenv root)"/plugins/rbenv-vars $ curl -fsSL https://github.com/rbenv/rbenv-installer/raw/main/bin/rbenv-doctor | bash $ rbenv install 3.0.3

I use rbenv-installer, it automatically installs ruby-build.

sudo apt-get update sudo apt-get -y install git pkg-config protobuf-compiler libprotobuf-dev libssl-dev wget build-essential sudo apt install -y cmake clang libclang-dev curl libz-dev screen net-tools curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.37.2/install.sh | bash curl -sSL https://git.io/g-install | sh -s sudo apt install curl autoconf bison libyaml-dev libreadline6-dev zlib1g-dev libncurses5-dev libffi-dev libgdbm6 libgdbm-dev libdb-dev curl -fsSL https://github.com/rbenv/rbenv-installer/raw/master/bin/rbenv-installer | bash echo 'export PATH="$HOME/.rbenv/bin:$PATH"' >> ~/.bashrc echo 'eval "$(rbenv init -)"' >> ~/.bashrc source ~/.bashrc rbenv install 2.7.2 rbenv global 2.7.2 gem install bundler sudo apt install nginx sudo apt install mysql-server sudo mysql_secure_installation sudo apt install php-fpm php-mysql sudo apt install php7.4-bcmath php7.4-bz2 php7.4-curl php7.4-dev php7.4-gd php7.4-imap php7.4-intl php7.4-json php7.4-ldap php7.4-mbstring php7.4-opcache php7.4-tidy php7.4-xml php7.4-snmp php7.4-readline php7.4-xsl php7.4-zip

Run rbenv-doctor script to verify installation

The main issue most people have with asdf is that it’s annoyingly slow. Not unusably so, but just enough that it’s irritating.

I identified [0] the source for much of it (sub-shells and pipes) and began a PR [1], but became bogged down with BATS testing, and then found mise / rtx, so kind of lost interest. Sorry. You can always implement these if you’d like.

[0]: https://github.com/asdf-vm/asdf/issues/290#issuecomment-1383...

[1]: https://github.com/asdf-vm/asdf/pull/1441

Or if you need to manage more than just node, asdf has been around for over a decade and works great. You can use a .tool-versions to change runtimes for each project you have, in addition to managing your global runtime versions

https://asdf-vm.com/

Why not just use a tool like asdf (https://asdf-vm.com/) or mise (https://mise.jdx.dev/)?

These tools have the advantage of not being multi-taskers and can manage version for all your tools. You wouldn’t need pyenv and npm and rvm and…

We’ve even started committing the .mise.toml files for projects to our repos. That way, since we work on multiple projects that may need multiple versions of the same tool, it’s handled and documented.

The purpose of a version manager is to help you navigate or install any tools for development easily. Version Manager can be one tool for each dependency (e.g. NVM, g) or One tool for all dependencies (e.g. asdf, mise).

(asdf)[https://asdf-vm.com/] fully supports Python and almost any other language. I've been using it for Ruby, Python, Elixir, and other languages for years and never looked back.

Secondly, our development environments must not drift, because then code may behave differently and a change could pass on our machine but fail in production. There are many tools for locking down environments, e.g nix, pkgx, asdf, containers, etc., and they all share the common goal of being able to lock down dependencies for an environment accurately and deterministically. And that needs to be enforced in our local workflow so we don't have to rely on CI environments for correctness. All developers must have environments that are effectively identical to what runs in CI (which itself should be representative of the production environment).

There are many ways this can be done (e.g nix, pkgx, asdf, containers, etc.), and we won’t get into which specific tools to use, because we'll instead cover the essential essence of preventing environment drift: