Webi is how developers install their tools.
Webi is how developers install their tools.
webi
webi webi
Since webi
is just a small helper script, it's always update on each use.
webi
is what you would have created if you automated how you install your common tools yourself: Simple, direct downloads from official sources, unpacked into~/.local
, added toPATH
, symlinked for easy version switching, with minimal niceties like resuming downloads and 'stable' tags.
You can install exactly what you need, from memory, via URL:
curl https://webinstall.dev/node@lts | bash
Or via webi
, the tiny curl | bash
shortcut command that comes with each
install:
webi node@lts golang@stable flutter@beta rustlang
You can see exactly what PATHs have been edited:
pathman list
And where:
cat ~/.config/envman/PATH.env
These are the files that are installed when you use webinstall.dev:
# Mac, Linux
~/.local/bin/webi
~/.local/bin/pathman
~/.local/opt/pathman-*
# Windows 10
~/.local/bin/webi.cmd
~/.local/bin/webi.ps1
~/.local/bin/pathman.exe
~/.local/opt/pathman-*
Assuming that you don't use pathman
for anything else, you can safely remove all of them.
If you use webinstall.dev again in the future they will be reinstalled.
Additionally, these files may be modified to update your PATH
:
~/.bashrc
~/.profile
~/.config/fish/config.fish
~/.config/envman/PATH.env
It's probably best to leave them alone.
Except where noted otherwise (such as wsl
) Webi installs everything into ~/.local/bin
and ~/.local/opt
.
Some programs also use ~/.local/share
or ~/.config
- such as postgres
and fish
- and
some use program-specific directories - such as Go, which uses ~/go/bin
.
If you want to remove any of them, simply deleting them should do well enough - just check the Cheat Sheet for any special notes.
Here are some examples:
# Remove jq
rm -rf ~/.local/bin/jq
rm -rf ~/.local/jq-*/
# Remove node.js
rm -rf ~/.local/opt/node/
rm -rf ~/.local/opt/node-*/