ssh-hosts.env.dist

# SSH-host parallelism for balancing:telemetry / balancing:telemetry-multiplayer's
# own real-time-costly data collection — distributed via the balancing:campaign /
# balancing:campaign-multiplayer orchestrators, which spawn one instance of the
# underlying telemetry script per combo/host in the first place. A one-shot
# telemetry script has no lane/queue concept of its own to plug SSH into
# directly; the orchestrator layer is what this file's hosts actually feed.
# See notes / doc/dev/balancing-telemetry.md.
#
# This file itself is auto-managed — you don't normally need to hand-edit
# it. Adding a new host is one command:
#   node scripts/setup-ssh-lane-host.mjs user@newhost
# a real interactive SSH session (you may be prompted for your sudo
# password, same as running the commands by hand) that installs git/a
# modern Node if missing, Playwright's Chromium system dependencies, clones
# the repo, and runs `npm ci` — everything the automated
# `balancing:campaign`/`balancing:campaign-multiplayer` runs themselves need.
# Once setup succeeds, the host is appended here *automatically* — no
# separate manual edit, no copying this `.dist` file by hand. Debian/Ubuntu
# only (see scripts/setup-ssh-lane-host.mjs's own doc comment for why).
#
# Auth is entirely external: whatever a plain `ssh user@host` would already
# use (a pre-unlocked key in your local ssh-agent, or a ~/.ssh/config
# alias) — this file (gitignored, never committed) never holds credentials,
# just `user@host` lines.
#
# Blank lines and lines starting with # are ignored. An empty or missing
# ssh-hosts.env just means "local lanes only" — this file is entirely
# optional. To re-run setup on every already-listed host at once (e.g.
# after a system update wiped a host's Node install), run the same script
# with no arguments — it reads this file and iterates every line, and
# re-adding an already-listed host is a safe no-op.
#
# alice@192.168.1.50
# bob@build-box.lan