Skip to content

Installation

Terminal window
curl -fsSL https://raw.githubusercontent.com/1rowvy/outry/master/install.sh | sh

The script downloads a static binary from the latest release (x86_64 or aarch64 — works on any distribution, including Alpine), verifies its SHA-256 checksum and installs it to ~/.local/bin/outry. It also sets up tab completion for fish and bash; for zsh add source <(outry completions zsh) to ~/.zshrc. Completions are generated by the installed binary, so they stay current after outry update.

Options are passed as environment variables:

Terminal window
# a specific version
curl -fsSL https://raw.githubusercontent.com/1rowvy/outry/master/install.sh | OUTRY_VERSION=v0.2.0 sh
# for all users (later update with `sudo outry update`)
curl -fsSL https://raw.githubusercontent.com/1rowvy/outry/master/install.sh | sudo OUTRY_INSTALL_DIR=/usr/local/bin sh
Terminal window
outry update # download and install the latest release (SHA-256 verified)
outry update --check # only check whether a new version exists

Like npm, Outry checks for a new version in the background once a day and prints a short notice after a command when one is available. Commands never wait for the network. The notice is not shown when output is piped, in CI, or with OUTRY_NO_UPDATE_NOTIFIER=1.

Terminal window
rm ~/.local/bin/outry # the binary
rm ~/.config/fish/completions/outry.fish # tab completion
rm ~/.local/share/bash-completion/completions/outry
rm -rf ~/.local/share/outry ~/.cache/outry # saved values, history, cached responses

On macOS the data lives in ~/Library/Application Support/outry and ~/Library/Caches/outry. Secrets stay in the system keychain: remove them with outry secret rm <NAME> --env <ENV> before deleting the binary, or in the keychain app (entries named outry). Your .outry files and env.toml are part of your repositories and are not touched.

To reinstall from scratch, run the commands above and then the install script again.

Installers for macOS (.dmg), Windows (.exe, .msi) and Linux (AppImage, .deb, .rpm) are on the releases page.

The app updates itself: on start it checks for a new version and offers to install it and restart. Updates are signed and verified. On Linux only the AppImage self-updates; .deb and .rpm are updated by downloading the new package.