Use Nix tooling in Forgejo actions
Some checks failed
deploy-cloudflare / checks (push) Failing after 39s
ci-gates / checks (push) Failing after 41s
deploy-cloudflare / deploy (push) Has been skipped

This commit is contained in:
Conrad Kramer 2026-06-10 03:35:53 -07:00
parent 91dad67fc2
commit d7f76d6ab2
No known key found for this signature in database
3 changed files with 26 additions and 169 deletions

View file

@ -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.