Install argiope

Pick the quickest route to a working binary.

The website publishes the repository install scripts directly, while releases keep the cross-platform archives ready for manual setup.

GitHub Pages script hosting Snap package Source build with Zig 0.15.2+
📦

Snap

sudo snap install argiope

Best fit when you want a fast Linux install without managing the release archive yourself.

🗂️

Release archives

https://github.com/christianhelle/argiope/releases/latest

Published builds cover Linux x86_64, Linux aarch64, macOS x86_64, macOS aarch64, and Windows x86_64.

🧱

Source build

git clone https://github.com/christianhelle/argiope.git
cd argiope
zig build -Doptimize=ReleaseFast

The optimized binary ends up at `zig-out/bin/argiope`.

🔧

Makefile install

make install INSTALL_DIR=~/.local/bin

Convenient when you are already building locally and want a user-scoped install path.

Verify the install

Check the version

argiope --version

If the command resolves, the shell can already find the installed binary.

Run a smoke test

argiope check https://example.com --depth 1

A small crawl is enough to verify networking, output formatting, and general installation health.

PATH issues: if `argiope` is not found after install, open a new terminal session first. On Windows, the PowerShell script updates the user PATH but existing terminals do not reload it automatically.

What each script does

`install.sh`

Detects Linux vs macOS, maps CPU architecture to the matching release asset, downloads the `.tar.gz`, and installs `argiope` with executable permissions.

`install.ps1`

Fetches the latest release metadata through the GitHub API, downloads the Windows zip, expands `argiope.exe`, and updates the user PATH if needed.

Pages endpoints

The workflow copies the repo-root scripts into the deployed site so the install URLs stay short and predictable.