Use local Forgejo runner label
This commit is contained in:
parent
b49dcff27d
commit
81724b7030
5 changed files with 9 additions and 7 deletions
|
|
@ -47,5 +47,7 @@ status, and first observable canvas frame when the browser exposes it.
|
|||
Ship the static web change with the existing Worker asset deploy and roll the publisher hotpatch
|
||||
binary to the LA nodes so their catalogs match the current watcher schema. Validate with clean-cache
|
||||
desktop/mobile browser loads and check the app's `window.__ecPerf` marks plus a live tune through the
|
||||
public relay. Teardown is removing the HTML seed/cache/warmup path, returning to live-API-only station
|
||||
rendering, and explicitly passing `--passthrough=false` only if an older watcher path is restored.
|
||||
public relay. The Forgejo workflows use the locally registered `namespace-profile-linux-medium`
|
||||
runner label so the Cloudflare deploy can actually leave the queue on the self-hosted forge.
|
||||
Teardown is removing the HTML seed/cache/warmup path, returning to live-API-only station rendering,
|
||||
and explicitly passing `--passthrough=false` only if an older watcher path is restored.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue