Is there a way to use asdf as system global?

[niksfirefly]

I wonder Is there a way to use asdf as global for every user?
to not duplicate plugins and save disks space.

[vic]

Yes! ASDF is pretty much agnostic to where it is installed. Just clone asdf at any shared location, say /opt/asdf and make sure all users have permissions for reading and executing binaries installed there. Have their shell profile source the asdf.sh environment and violá.

I'd recommend having a single user manage installed tool versions, since asdf has no restriction on what a plugin-install command can do, and what permissions files are created with. So, I guess the best would be, install things for other users and make sure everyone can read and execute.

[niksfirefly]

unfortunately plugins go to $HOME/.asdf dir
instead /opt/asdf

[niksfirefly]

export ASDF_DATA_DIR=/opt/asdf
make the trick, so far so good

[gfsheppard]

Make sure to export ASDF_DATA_DIR before calling the scripts in.bashrc.

export ASDF_DATA_DIR=/opt/asdf
. /opt/asdf/asdf.sh
. /opt/asdf/completions/asdf.bash

Says so here, but I missed it, and it kept looking at my local installation.

[chavenor]

export ASDF_DATA_DIR=/opt/asdf
. /opt/asdf/asdf.sh
. /opt/asdf/completions/asdf.bash

Is this before installing via git or after?

[elcritch]

export ASDF_DATA_DIR=/opt/asdf
. /opt/asdf/asdf.sh
. /opt/asdf/completions/asdf.bash

Is this before installing via git or after?

It should be after, but it probably doesn't matter.

Note for others, you may want to copy the $HOME/.tool-versions file to other users to set their default versions.

[donnydongchen]

We may also need to add export ASDF_DIR=/opt/asdf to the shell profile. It complained if I didn't do this.