rbenv VS ruby-build

When I was technical blogging on how to learn from open-source code [1], I used it quite frequently to get unstuck and/or to figure out how to tease apart a large question into multiple smaller functions. For example, I had no idea how to break up this long `sed` command [2] into its constituent parts, so I plugged it into ChatGPT and asked it to break down the code for me. I then Googled the different parts to confirm that ChatGPT wasn't leading me astray.

If I had asked StackOverflow the same question, it would have been quickly closed as being not broadly applicable enough (since this `sed` command is quite specific to its use case). After ChatGPT broke the code apart for me, I was able to ask StackOverflow a series of more discrete, more broadly-applicable questions and get a human answer.

TL;DR- I quite like ChatGPT as a search engine when "you don't know what you don't know", and getting unblocked means being pointed in the right direction.

1. https://www.richie.codes/shell

2. https://github.com/rbenv/rbenv/blob/e8b7a27ee67a5751b899215b...

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.

By setting up your environment in isolation, you can prevent yourself from a lot of issues when experimenting with code. It makes your code behave more predictable due to the defined state of the runtime environment you are working with. This article should provide you with enough information to get started, but obviously, there is a lot more power embedded in NVM, Virtual Environment and RBEnv. So make sure to check their documentation.

There is this good resource that also talk about different ruby version manager from the Rbenv repository. With some links to benchmarks of ASDF and Rbenv.

rbenv (my personal favorite)

One suggestion would be to setup your install based on a development environment using git and a Ruby version manager like rvm or rbenv to allows you to setup a user controlled gemset and execution path.

rbenv for Ruby

git clone https://github.com/rbenv/rbenv.git ~/.rbenv

On MacOS, I haven't had a problem with character encodings in the terminal in ruby for a while, but used to. When I used to, it had to do with how ruby had been installed, in particular that it needed to be compiled linking against an appropriate readline library. Are you trying to use the ruby that came with debian? You might have more luck installing ruby yourself, and using a ruby version manager. rbenv might be the simplest for you.

For my local machine, I use RVM (head). Other options are rbenv and 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.