Skip to content

Install

loadout is a single static binary with no runtime dependencies. It runs on Linux and macOS, on amd64 and arm64.

Pick one channel and stay on it. Which tool installed the binary determines which tool can update it, and loadout update refuses to overwrite a file another package manager owns.

Terminal window
curl -fsSL https://loadout.makery.tools/install.sh | sh

Installs into ~/.local/bin. This is the right choice on a server, or anywhere you do not want a package manager involved.

The script is POSIX sh so it runs on a minimal machine. It resolves the latest release, downloads the tarball for your platform over HTTPS, verifies the published checksum before putting anything on your PATH, and installs by writing to a temporary file and renaming it into place, so an interrupted run cannot leave a half-written executable behind.

LOADOUT_BASE_URL points it at a mirror if you have one.

Terminal window
brew tap loadoutsh/loadout
brew install loadout

Works on macOS and on Linuxbrew. Upgrades come through brew upgrade loadout — loadout update will decline and print that command instead, because overwriting a Homebrew-managed file behind its back leaves brew reporting a version it never installed.

Terminal window
go install github.com/loadoutsh/loadout/cmd/loadout@latest

Puts the binary in $GOBIN (or $GOPATH/bin). Same ownership rule: the Go toolchain installed it, so go install updates it.

Builds this way carry no embedded version string from the release process, so loadout version reports a development build and loadout update will tell you it cannot compare versions rather than guessing.

Terminal window
loadout version

If the command is not found, the install directory is not on your PATH. For the script that is ~/.local/bin:

Terminal window
export PATH="$HOME/.local/bin:$PATH"

Add that to your shell configuration if it is missing. loadout will not add it for you.

Installing the binary does nothing to your shell. Nothing changes until you run loadout init and loadout apply and add one line — see Getting started.