Run Hydrascale

The daemon needs Linux and root, because it creates network namespaces. There are two ways to see a change working, and the right one depends on what changed.

The console alone, on a developer machine

Use this for a console change. It needs no root and no Linux.

The console is static files under internal/ui/static. Serve them and point the console at a recorded API response:

cd internal/ui/static && python3 -m http.server 9443

Open http://127.0.0.1:9443. The console shows its error state, because no daemon answers /api/status. To see a populated console, run the Go test harness instead, which serves the static files with a fake daemon behind them:

go test ./internal/ui/... -run TestConsoleServer -v

The whole daemon, on the test host

Use this for anything that touches the host network. Deploy with the verify-on-phobos skill, then forward the console port:

ssh -L 9443:127.0.0.1:9443 phobos

Open http://127.0.0.1:9443 on your own machine. The console binds the loopback address on the test host only; the SSH forward is the supported way to reach it.

Configuration for a local run

contrib/dev-config.yaml declares two tailnets with no auth key. It drives the console against a daemon that cannot connect, which is the state that most needs a designed empty view. Use it when you change an empty state.

sudo hydrascale serve --config contrib/dev-config.yaml

How to tell it is up

curl -s --unix-socket /var/lib/hydrascale/api.sock http://local/api/status | head -20
curl -s -H 'X-Hydrascale-Console: 1' http://127.0.0.1:9443/api/status | head -20

The daemon logs the console address at start, with the statement that the console has no authentication. If that line is missing, the console listener did not start; check console.enabled and console.bind_address in the configuration.