ruby-build VS asdf

Let’s get started. I prefer to manage my Ruby installations on my development machine with chruby paired with ruby-install. Another outstanding set of tools is rbenv with ruby-build. I highly recommend installing Ruby with one of those two sets of tools. Follow the instructions on their project’s READMEs. For this article, I’ll be running Ruby (MRI) v3.3.0.

Seems someone was able to fix your problem with openssl installed from linuxbrew, see herehttps://github.com/rbenv/ruby-build/discussions/2199

git clone https://github.com/rbenv/ruby-build.git ~/.rbenv/plugins/ruby-build

$ 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

Great! Already available via ruby-build on rbenv!

# Part One: Install basics # zlib1g-dev might be zlib-dev on Ubuntu 22.04 # lsb-release might be lsb_release on Ubuntu 22.04 sudo apt-get update && sudo apt-get -y install \ git \ ca-certificates \ curl \ gnupg \ build-essential \ lsb-release \ zlib1g-dev \ libssl-dev \ zsh && \ sh -c "$(curl -fsSL https://raw.github.com/robbyrussell/oh-my-zsh/master/tools/install.sh)" # Part Two: Installs & sets up rbenv, installs ruby git clone https://github.com/rbenv/rbenv.git ~/.rbenv && \ echo 'eval "$(~/.rbenv/bin/rbenv init - zsh)"' >> ~/.zshrc && \ source ~/.zshrc && \ git clone https://github.com/rbenv/ruby-build.git "$(rbenv root)"/plugins/ruby-build && \ rbenv install 3.1.2 && \ rbenv global 3.1.2 # Part Three: Optional minimum setup for Rails development echo "gem: --no-document" >> ~/.gemrc && \ gem install bundler && \ gem install rails

I'm using rbenv to manage Ruby versions, and it turns out they recently started building Ruby with OpenSSL 3.0 instead of OpenSSL 1.1.

ruby-build Wiki is good to learn.

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:

I've really been enjoying asdf, which is a program that allows you to install specified versions of dev utilities as well as dynamically manage them via shims and .tool-versions files.