Run Forgejo actions on forge
This commit is contained in:
parent
81724b7030
commit
5d0f3077d3
2 changed files with 49 additions and 3 deletions
|
|
@ -48,6 +48,7 @@ Ship the static web change with the existing Worker asset deploy and roll the pu
|
|||
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. 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.
|
||||
runner label and ecp-forge runs a persistent `forgejo-runner-agent` service with a normal shell
|
||||
tool PATH 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