Appearance
Installation
Three install modes are real today. Two more are documented as target state for completeness; pages explicitly mark "not yet shipped" and point at the working alternative.
Real today
| Mode | When to use | Page |
|---|---|---|
Local install (hivecast install --home <path>) | Per-user laptop, dev workstation, macOS, Windows, inside a container with its own init | Local install |
Linux systemd via .deb | Production Linux deployment with systemd-managed hivecast-nats.service and hivecast-host.service | Linux systemd |
| Docker / container mode | Worker cells (projects/matrix-worker/); same .deb payload running inside a container | Docker / container mode |
The Linux .deb is built by projects/matrix-3/packages/hivecast/scripts/build-deb-installer.js. The default install URL is https://hivecast.ai/downloads/hivecast_<version>_amd64.deb.
Target state
Status: target state — not yet shipped. Filed as P1.16b. Documented for completeness; both platforms can use the local install today.
| Mode | When to use | Page |
|---|---|---|
| macOS launchd plist | macOS service install | macOS launchd |
| Windows Service | Windows service install | Windows Service |
Pages
- Local install — present state.
- Service install — what "service install" means in general, and which platforms have one.
- Linux systemd — present state, real today.
- macOS launchd — target state.
- Windows Service — target state.
- Docker / container mode — present state for the worker-cell container at
projects/matrix-worker/.
NATS is mandatory and always-up
NATS is a service-class dependency. The .deb installs a separate hivecast-nats.service so a Host crash does not take NATS down. The local install spawns NATS as an independent sibling process for the same reason (see hivecast.mjs:561-723). Any install path that runs NATS as a child of host-service is wrong for production.
Default runtime set
A fresh hivecast install registers the default runtimes defined in projects/matrix-3/packages/hivecast/bin/hivecast.mjs:28-39. Today this is one runtime per package (~12 runtimes total).
Status: target state — multi-package grouping (P1.40-a). When P1.40-a lands, default-runtime grouping co-tenants
shared-isolation packages by substrate role (CONTROL-PLANE,USER-APPS); the result is ~4 runtimes per Host. The default install command is unchanged; only the internal grouping changes. See P1.40.