Container image: releases only, a token by default, lean layers; every action pinned
The image is published to GHCR as the release's version when a release dispatches docker.yml, and never as latest or per commit. Pushes and pull requests that touch it build it and try headless (with and without a token) and browser mode, without publishing. The image: node:24-slim pinned by digest (the major CI tests on), npm ci from the lockfile in its own layer, only src, site, scripts and the harness copied in (an allow-list .dockerignore), root-owned and run as node, /saves ready for --save-dir. The entrypoint runs the servers with node directly and, with no SOT_MCP_TOKEN, makes a token for the run and prints it (MCP_NO_TOKEN=1 to opt out); the docs publish ports to 127.0.0.1 and explain --allow-host. Labels, SBOM and provenance on push. Every GitHub Action in every workflow is pinned to a commit SHA with its version, and Dependabot keeps the actions, the image's base and the npm tools current. tests/docker.test.js guards all of it. The ADR and the github-pages skill say the image is a tool: GHCR only, never Pages.
This commit is contained in:
parent
9c8cda44c1
commit
98735eb769
16 changed files with 367 additions and 110 deletions
|
|
@ -35,6 +35,9 @@ one, redesign the feature.
|
|||
run on a developer's own machine against a checkout; nothing they serve is deployed, and the game
|
||||
never depends on them. Their code stays out of `_site/` (`src/agent/` is development-only, see
|
||||
`docs/adr/0004-dev-only-code.md`).
|
||||
- **The container image is a tool too.** `docker/` packages those tools; `docker.yml` publishes it to GHCR for releases
|
||||
(version tags only, no `latest`) and never to Pages. Someone may run its development server where they like; that is
|
||||
not a host of the game, and the game never depends on it.
|
||||
|
||||
## How it deploys
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue