Commit graph

5 commits

Author SHA1 Message Date
f2992d2d0e
ci: stop using FORGEJO_* secret names
All checks were successful
Build and Deploy to Production / check (push) Successful in 5s
Build and Deploy to Production / build (push) Successful in 12s
Build and Deploy to Production / deploy (push) Successful in 18s
Forgejo reserves names starting with FORGEJO_, and since runner v13
secrets.FORGEJO_TOKEN, _USER and _REGISTRY no longer reach the job as
the values set on the repository: Kaniko logged in with the wrong
credentials and every image push failed with UNAUTHORIZED.

The registry host and user are not secret (they are in every image
name), so write them in the workflow; the token comes from FJ_TOKEN,
as in datacenterbingo.

Assisted-by: Claude:opus-5-5
2026-11-13 01:47:28 +04:00
e382992c2e Merge pull request 'chore: Configure Renovate' (#1) from renovate/configure into main
Some checks failed
Build and Deploy to Production / check (push) Successful in 6s
Build and Deploy to Production / build (push) Failing after 1s
Build and Deploy to Production / deploy (push) Has been skipped
Reviewed-on: #1
2026-11-12 20:36:09 +00:00
b982d258e1 deps: add renovate.json
All checks were successful
Test / check (push) Successful in 21s
2026-11-12 20:33:22 +00:00
6e2cc3c153
Set nix options through NIX_CONFIG in CI
Some checks failed
Build and Deploy to Production / check (push) Successful in 20s
Build and Deploy to Production / build (push) Failing after 1s
Build and Deploy to Production / deploy (push) Has been skipped
The runner mounts a persistent nix-store volume over /nix, and the
nixos/nix image makes /etc/nix/nix.conf a symlink into /nix/store. When
the volume and image versions differ, the link dangles and appending to
it fails before checkout. That broke asxpio and datacenterbingo CI on
2026-10-18.

Pass the settings in NIX_CONFIG instead, with build-users-group empty
and the sandbox off as the image config has them.

Assisted-by: Claude:opus-5-5
2026-10-18 09:48:30 +04:00
a4b677f898
blog: Zola site, nginx image, Forgejo deploy pipeline
All checks were successful
Build and Deploy to Production / check (push) Successful in 9s
Build and Deploy to Production / build (push) Successful in 25s
Build and Deploy to Production / deploy (push) Successful in 36s
2026-07-16 19:51:31 +04:00