hey mit Homebrew installieren

Projektlinks

• Homepage

Befehle und Aliase

• hey

Projektgeschichte

The GitHub repository was created in September 2016. The README explains the naming history: the project was originally called boom, was influenced by Tarek Ziade's boom, and was renamed to hey to avoid binary-name conflicts and preserve the original boom name for its owner.

The project stayed deliberately small: a single-purpose executable with flags for request count, concurrency, rate limiting, duration-based runs, output format, HTTP method, headers, body data, basic auth, proxy, keep-alive behavior, redirects, CPU count, and HTTP/2.

Adoptionsgeschichte

Homebrew packaging is documented directly in the README, and the batch metadata lists additional package-manager coverage in Alpine, Debian, MacPorts, Nix, Ubuntu, and openSUSE/Zypper. That spread reflects hey's role as a drop-in CLI utility for quick HTTP load checks.

GitHub release pages show tagged 0.1.x releases and downloadable assets, including platform binaries in older releases. Later release notes document community pull requests and additions such as Dockerfile support, CI, DNS-output fixes, dependency upgrades, and a request-function hook for library-style traffic variation.

Wie es verwendet wird

The common use is intentionally direct: run hey against a URL, optionally choose total requests with -n, concurrency with -c, duration with -z, per-worker QPS with -q, and method/body/header options for non-GET requests. The README examples cover default requests, a 1000-request/100-worker run, duration-based load, POST bodies, custom headers, HTTP/2, and rate limiting.

The tool sits between curl-style manual checks and heavier load-testing systems. It is most useful when a developer, operator, or package maintainer wants a quick repeatable command that can be installed with the local package manager and run without a service or scenario file.

Warum Paket-Nerds sich dafür interessieren

hey is package-nerd significant because ApacheBench is ubiquitous but historically tied to Apache httpd packaging. hey gives users a small standalone Go binary with a modern CLI surface, HTTP/2 support, and easy cross-platform distribution.

The rename from boom to hey is also a packaging lesson: executable names collide, and a short memorable binary name only works if it does not trample an existing tool's namespace.

Zeitleiste

• 2016-09: GitHub repository metadata records creation of rakyll/hey.
• 2016: The README records the rename from boom to hey after conflicts with Tarek Ziade's boom.
• 2010s: README installation notes include platform binaries and Homebrew packaging.
• 2020s: Release notes document continued maintenance through 0.1.x tags, including request-generation hooks, Dockerfile support, CI, and dependency updates.

Related projects

• Related tools include ApacheBench (ab), Tarek Ziade's boom, wrk, vegeta, bombardier, curl for single-request checks, and larger scenario-based load-testing systems.

Quellen

• GitHub README provides the origin/rename explanation, ApacheBench-replacement description, installation, package-manager note, usage flags, HTTP/2 support, and examples.
• GitHub release pages provide tagged release history and maintenance notes.
• Homebrew formula metadata and the input package-manager map support the package-manager adoption summary.