IPFS install manager
$ npm i -g iim
Note: Windows not yet supported!
Example - Use the latest version of Kubo
$ iim use kubo
✔ selected kubo version 0.24.0
✔ installed kubo 0.24.0
✔ installed binary at /Users/alan/.iim/dists/kubo@0.24.0/ipfs
✔ initialized IPFS at /Users/alan/.iim/kubo@0.24.0
✔ configured IPFS
✔ symlinked /Users/alan/.iim/dists/kubo@0.24.0/ipfs -> /Users/alan/.iim/dists/current
✔ symlinked /Users/alan/.iim/dists/kubo@0.24.0/ipfs -> /usr/local/bin/ipfs
🚀 IPFS is ready to use
$ ipfs version
kubo version: 0.24.0
Example - Use Kubo at version 0.23.0
$ iim use kubo 0.23
✔ selected kubo version 0.23.0
✔ installed kubo 0.23.0
✔ installed binary at /Users/alan/.iim/dists/kubo@0.23.0/ipfs
✔ initialized IPFS at /Users/alan/.iim/kubo@0.23.0
✔ configured IPFS
✔ symlinked /Users/alan/.iim/dists/kubo@0.23.0/ipfs -> /Users/alan/.iim/dists/current
✔ symlinked /Users/alan/.iim/dists/kubo@0.23.0/ipfs -> /usr/local/bin/ipfs
🚀 IPFS is ready to use
$ ipfs version
kubo version: 0.23.0
A new repo is created and used for each implementation/version combination at ~/.iim/kubo@0.24.0
, for example.
Adds a symlink at /usr/local/bin/ipfs
that points to a script that runs IPFS with IPFS_PATH
set to ~/.iim/kubo@0.24.0
.
IPFS is installed to ~/.iim/dists/kubo@0.24.0/node_modules/ipfs
or ~/.iim/dists/go-ipfs@0.4.18/node_modules/go-ipfs-dep
for example.
Looks like this:
$ iim use kubo
✔ selected kubo version 0.4.18
✔ installed kubo 0.4.18
✔ installed binary at /home/dave/.iim/dists/kubo@0.4.18/ipfs
✔ initialized IPFS at /home/dave/.iim/kubo@0.4.18
✔ symlinked /home/dave/.iim/dists/kubo@0.4.18/ipfs -> /home/dave/.iim/dists/current
✖ failed to symlink /home/dave/.iim/dists/kubo@0.4.18/ipfs -> /usr/local/bin/ipfs
💥 failed to link binary at /usr/local/bin/ipfs, try running sudo iim link
Don't worry! Mostly everything worked fine - you just don't have permission to write to /usr/local/bin
! Just run sudo iim link
and it'll try again to create that symlink.
Feel free to dive in! Open an issue or submit PRs.
MIT © Alan Shaw