Install

iroh-forge ships two commands: iroh-forge (the CLI and pinner) and git-remote-iroh (the git helper that handles iroh:// URLs). Both must be on your PATH.

Prebuilt package (linux-64)

pixi global install -c https://prefix.dev/nandi-testing -c conda-forge iroh-forge

This puts iroh-forge and git-remote-iroh in ~/.pixi/bin. Every push to main publishes a new build to the nandi-testing channel; update with pixi global update iroh-forge.

Check that git can find the helper:

command -v git-remote-iroh
iroh-forge id                 # prints this machine's client id

From source with pixi

The repo's pixi.toml brings its own Rust toolchain:

git clone https://gitlab.latha.org/nandi/iroh-forge && cd iroh-forge
pixi run install              # into ~/.local/bin
pixi run install /usr/local   # or another prefix (binaries go in <prefix>/bin)
pixi run doctor               # checks git can find git-remote-iroh

pixi run install-local installs into the pixi env instead, so pixi run git clone iroh://... works without touching PATH.

With cargo

cargo install --path .
iroh-forge install-helper     # puts git-remote-iroh next to the binary

git-remote-iroh is a symlink to iroh-forge.

State and logs

Keys and data live in ~/.iroh-forge (override with IROH_FORGE_HOME). Set IROH_FORGE_LOG=info for logs.