Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more
Go to file
2022-06-01 15:12:32 -04:00
.github fix: update event trigger for doc-version workflow (#1232) 2022-05-20 09:07:11 -04:00
bin Update code to use . instead of source 2021-05-21 12:03:06 -04:00
completions fix: completions for asdf plugin list (#1061) 2021-09-30 08:24:03 -04:00
docs docs: ASDF_DIR/ASDF_DATA_DIR absolute paths (#1225) 2022-05-17 08:03:40 -04:00
lib fix: always use ASDF_DEFAULT_TOOL_VERSIONS_FILENAME for filename when present (#1238) 2022-05-27 07:50:04 -04:00
scripts ci: automated release workflow (#987) 2021-07-13 11:32:37 +10:00
test fix: always use ASDF_DEFAULT_TOOL_VERSIONS_FILENAME for filename when present (#1238) 2022-05-27 07:50:04 -04:00
.editorconfig Add .editorconfig file. 2019-11-25 12:08:31 -06:00
.gitattributes feat: Elvish Shell support (#1066) 2021-11-18 21:05:27 +11:00
.gitignore feat: Elvish Shell support (#1066) 2021-11-18 21:05:27 +11:00
.tool-versions fix: remove comments from whole file instead of line by line for performance (#1198) 2022-04-08 10:44:07 -04:00
asdf.elv fix: update elvish to 0.18.0 2022-04-22 07:50:53 -04:00
asdf.fish fix: make fish shell setup match other shells (#1209) 2022-04-21 09:40:43 -04:00
asdf.sh fix: Prevent unbound variable error with nounset in asdf.sh (#1158) 2022-01-19 17:00:53 -05:00
ballad-of-asdf.md fix ballad formatting 2017-06-10 10:06:48 -04:00
CHANGELOG.md chore: release 0.10.1 (#1211) 2022-05-18 07:54:06 -04:00
CONTRIBUTING.md docs: rewrite using Vuepress (#1000) 2021-07-23 15:26:21 +10:00
defaults Add support for config file. 2016-04-24 22:39:24 +09:00
help.txt docs: Fix help text for 'asdf global' (#1150) 2022-01-04 14:09:27 -05:00
LICENSE Add license file. Thanks to @mosic for reporting 2016-03-16 10:27:58 +05:30
README.md fix: updating references to legacy github.io site (#1240) 2022-06-01 15:12:32 -04:00
SECURITY.md chore: sec details & update supported version (#825) 2020-11-10 19:39:13 +11:00
version.txt chore: release 0.10.1 (#1211) 2022-05-18 07:54:06 -04:00

asdf Lint Tests

Manage multiple runtime versions with a single CLI tool, extendable via plugins - docs at asdf-vm.com

asdf is a CLI tool that can manage multiple language runtime versions on a per-project basis. It is like gvm, nvm, rbenv & pyenv (and more) all in one! Simply install your language's plugin!

Why use asdf?

  • single CLI for multiple languages
  • consistent commands to manage all your languages
  • single global config keeping defaults in one place
  • single .tool-versions config file per project
  • support for existing config files .node-version, .nvmrc, .ruby-version for easy migration
  • automatically switches runtime versions as you traverse your directories
  • simple plugin system to add support for your language of choice
  • shell completion available for common shells (Bash, Zsh, Fish, Elvish)

Documentation

Please head over to the documentation site for more information!

Contributing

See CONTRIBUTING.md in the repo or the Contributing section on the docs site.

Community & Questions

  • FAQ
  • GitHub Issues GitHub Issues: report a bug or raise a feature request to the asdf core team
  • StackOverflow Tag StackOverflow Tag: see existing Q&A for asdf. Some of the core team watch this tag in addition to our helpful community

Ballad of asdf

Once upon a time there was a programming language
There were many versions of it
So people wrote a version manager for it
To switch between versions for projects
Different, old, new.

Then there came more programming languages
So there came more version managers
And many commands for them

I installed a lot of them
I learnt a lot of commands

Then I said, just one more version manager
Which I will write instead

So, there came another version manager
asdf version manager - https://github.com/asdf-vm/asdf

A version manager so extendable
for which anyone can create a plugin
To support their favourite language
No more installing more version managers
Or learning more commands


This was the mail I wrote to a few friends to tell them about the project. Thanks to @roshanvid for suggesting that this go into the readme
@HashNuke