Use Nix tooling in Forgejo actions
This commit is contained in:
parent
91dad67fc2
commit
d7f76d6ab2
3 changed files with 26 additions and 169 deletions
|
|
@ -52,3 +52,7 @@ runner label and ecp-forge runs a persistent `forgejo-runner-agent` service with
|
|||
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.
|
||||
|
||||
Forgejo CI and deploy jobs run inside the repository Nix dev shell instead of downloading generic
|
||||
Linux Rust, Trunk, age, or Node binaries. This keeps self-hosted NixOS runners reproducible and
|
||||
prevents dynamic-linker failures from blocking the Cloudflare asset rollout.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue