Installation
Release binaries
Section titled “Release binaries”Download the archive for your platform from GitHub Releases.
Release builds include Linux x86_64/ARM64 and macOS Intel/Apple Silicon;
inspect the chosen release’s assets for availability. Extract the binary,
place it on your PATH, and run tobaru --help.
The site currently documents dev, not a versioned release. Use a source build of the revision linked in the header when you need the exact documented behavior.
Build from source
Section titled “Build from source”Requires Rust 1.88 or newer, Cargo, Git, and a native C/C++ build toolchain for
the TLS dependencies. Replace SOURCE_COMMIT with the full commit linked in the
page header to build that exact revision:
git clone https://github.com/cfal/tobaru.gitcd tobarugit checkout SOURCE_COMMITCARGO_BUILD_JOBS=1 cargo install --locked --path .tobaru --helpThe first build requires GitHub access to fetch the pinned HTTP/2 fork. Cached
checkouts can support later offline builds. cargo install tobaru installs the
older crates.io release, not this source revision. Registry publishing is
intentionally blocked while these HTTP/2 fixes need
a Git dependency.
For a local build without installation:
CARGO_BUILD_JOBS=1 cargo build --release --locked./target/release/tobaru --helpPermissions
Section titled “Permissions”Start with a loopback listener on an unprivileged port. Binding privileged ports or managing Linux firewall rules requires additional permissions; ordinary forwarding does not require root. See iptables integration.
Continue with the first configuration.