Skip to content

distribution.md

Latest commit

 

History

History
37 lines (25 loc) · 1.43 KB

distribution.md

File metadata and controls

37 lines (25 loc) · 1.43 KB
Raw

Distribution

Where a published hensu comes from, and which channel to trust.

Channels

Channel Command
Go go install github.com/my-rv/hensu/cmd/hensu@latest
Homebrew (macOS) brew install --cask MY-RV/tap/hensu (tap)
Scoop (Windows) scoop bucket add my-rv https://github.com/MY-RV/scoop-bucket then scoop install hensu
Binaries Releases — archives, bare binaries, checksums.txt
Self-update hensu --update

Homebrew ships pre-built binaries as casks, and casks are macOS-only. On Linux use Go or the release binary.

Homes

Repo
MY-RV/hensu Source, releases, advisories
MY-RV/homebrew-tap Casks/hensu.rb, written by GoReleaser
MY-RV/scoop-bucket hensu.json, written by GoReleaser

The fully-qualified Homebrew name avoids clashing with unrelated taps.

Verifying what you got

sha256sum -c checksums.txt --ignore-missing

hensu --update does that check on its own and refuses a release that publishes no checksums — see install.md.

Not channels

No curl | sh installer, and no package in Homebrew core or Scoop Main. Both would mean asking people to trust something this project cannot yet vouch for.