5 Commits

Include renames

Author	SHA1	Message	Date
gregandClaude Opus 5.5	65cbb8cfd4	feat(ark): ready when advertising for join ... First boot with the install fix ran ARK for ~10 minutes and found, in ShooterGame.log: "Server: ... has successfully started!", "EOS ownership validation initialized: Success", "Full Startup: 36.26 seconds" and, about two minutes later, "Server has completed startup and is now advertising for join. (9.96GB Mem)". That last line is when players, console players through EOS included, can join, so it is the readyPattern; the real line is test.yaml's readyExample. Boot tests now wait for it instead of only checking ARK stays up for 10 minutes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-25 02:35:52 -04:00
gregandClaude Opus 5.5	9fef27cd40	fix(ark): retry the server install before handing over to the image ... The image's start_server runs SteamCMD once and carries on even when it fails; SteamCMD's intermittent "Missing configuration" error then left no server installed, so ARK exited and only the node's restart policy saved it (a boot test would fail on the restart). First boot showed it. The startup command now downloads SteamCMD if missing, runs the usual "+login anonymous +quit" warm-up and installs app 2430930, retrying up to three times until ArkAscendedServer.exe exists. start_server's own install step then only validates. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-25 02:25:45 -04:00
gregandClaude Opus 5.5	2ad445ffdd	fix(ark): run as the image's own user; honour custom RCON ports ... ARK's image is built around user gameserver (uid 25000) and locks /home/gameserver to it, so under the node's default 1000:1000 the startup script got "Permission denied" and the server restart-looped, on real nodes as well as in boot tests. Set containerUser 25000:25000 (needs node-agent and panel support for containerUser). The startup command read ${RCON_PORT}, but the node passes the RCONPort setting as RCONPORT, so custom RCON ports were ignored for 27020. Boot-tested in the Linux agent image: up 30 minutes with no restart. The test now waits 10 minutes, covering the first ~13 GB download. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-24 22:17:03 -04:00
gregandClaude Opus 5.5	e9ff989246	ci: boot-test changed games before publishing ... Only games whose folder changed are boot-tested (against the previous main commit, or against main on branches; manual runs pick games). Each one is deployed by the node-agent's real deploy code on a dedicated game-test runner, in a network that can reach the internet but not the LAN. Publishing to the panel runs only if they all booted. - boottest-payload builds the DEPLOY_SERVER message the panel would send - readyPattern/failPatterns in game.yaml; readyExample in test.yaml is checked against the pattern during validation - secrets in test.yaml come from CI; a game missing one is skipped - Minecraft gets a ready pattern; Dragonwilds needs DRAGONWILDS_OWNER_ID - RUNNER.md + scripts/runner: runner, isolated network, systemd unit Also fixes newline values ("\n" separators/footers) that yaml.v3 wrote as "" on import, which would have broken ARK and Dragonwilds config files once synced, and adds a round-trip test for the importer. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-24 17:49:19 -04:00
gregandClaude Opus 5.5	822b44e2e5	feat: game templates, schemas and validator ... Public game templates for GBR Hosting, one games/<id>/game.yaml per game, imported from the panel. A Go tool validates them against JSON Schemas and checks for credentials, private addresses and consents that default to accepted; CI runs it on every push. Admin/RCON passwords are no longer shared defaults: they are blank with x-generate so the panel creates one per server, and Palworld/ARK no longer publish their RCON/REST ports. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-24 16:54:21 -04:00