Skip to content

macOS installer cannot succeed from releases; /cli route is not CLI-only #273

Description

@manuschillerdev

Summary

The documented macOS install path does not currently produce a usable hypeman command.

curl -fsSL https://get.hypeman.sh | bash attempts the full server install on macOS, but the release artifacts it expects are not published. https://get.hypeman.sh/cli also redirects to the same full server installer instead of a CLI-only installer.

Reproduction

On Apple Silicon macOS:

curl -fsSL https://get.hypeman.sh | bash
command -v hypeman

Expected:

hypeman

Actual:

hypeman not found

Also:

curl -fsSLI https://get.hypeman.sh/cli

currently redirects to the full installer:

https://raw.githubusercontent.com/onkernel/hypeman/refs/heads/main/scripts/install.sh

What appears to be happening

In release mode on macOS, scripts/install.sh searches for a server release artifact shaped like:

hypeman_<version>_darwin_arm64.tar.gz

Current kernel/hypeman server releases appear to publish Linux artifacts only, for example:

hypeman_0.1.0_linux_amd64.tar.gz
hypeman_0.1.0_linux_arm64.tar.gz

Because the server install fails before CLI setup completes, the user ends up without hypeman in PATH.

Separately, /cli does not seem to be CLI-only; it returns the same full installer and therefore has the same failure mode.

Suggested fixes

  • Publish macOS server artifacts, or make macOS default to source build.
  • Make https://get.hypeman.sh/cli install only kernel/hypeman-cli.
  • Let CLI installation succeed even if server installation is unavailable.
  • Avoid requiring Docker CLI unconditionally on macOS if Docker is only needed for build features.
  • Update the README with the currently supported macOS install path.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions