I have my own script that does a full update of all installed software and I’ve included ASDF updating of all plugins in it for that exact reason, @AstonJ. It’s a bit manual but you can script it (like I did) and then forget about it.

@ohm One version manager for 99% of all languages and many tools and databases you’ll ever use, is my motivation. Using asdf definitely simplified my setup.

I think the biggest benefit is that you can use it for lots and lots and lots of different languages

Have a look at their list here:

In my dev env setup guide on my blog (link in first post) we use ASDF for Ruby, Elixir, Erlang and NodeJS

For Ruby in a production env, I’ve always used Chruby as it has always worked well:

I’m completely sold on asdf. With the .tool-versions file I can just asdf install in a project and go.

I also love how simple it is to have multiple versions of PostgreSQL running. I use the technique described here to manage the database per project so I know I’m always exactly matching the production version. This has been super helpful when one project is on Heroku and runs 12 or 13 and another is using AWS Aurora that’s more like 9.6 maybe 10.