jpnadas/finrod
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

drop Gitea Actions workflow (no runners on the homelab yet)

Browse Source 
Falls back to ./build.sh from the workstation. Re-add the workflow
when Gitea runners are wired up.
This commit is contained in:
João Pedro Battistella Nadas
2026-06-09 15:26:30 +02:00
parent 777c80a0e1
commit 94969a0f46
3 changed files with 18 additions and 50 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
README.md
View File

@@ -31,15 +31,30 @@ All three fit in radagast's 10 GB at Q4. Switching models in the dropdown forces
## Build / push image
CI: `.gitea/workflows/build.yml` builds multi-arch (amd64+arm64) on push to `main` and pushes to `rg.nl-ams.scw.cloud/valinor/finrod:{latest, <short-sha>}`. Requires a `SCW_SECRET_KEY` secret on the Gitea repo with a Scaleway IAM key that has `ObjectStorage:RegistryPush` on the `valinor` registry.
Built locally and pushed to Scaleway — no Gitea runners on the homelab yet, so there's no CI workflow.
Manual fallback if Gitea Actions isn't wired up:
One-time setup (host needs buildx + QEMU for cross-arch):
```sh
docker buildx create --name multi --use
docker run --privileged --rm tonistiigi/binfmt --install all
docker login rg.nl-ams.scw.cloud -u nologin -p <SCW_SECRET_KEY>
```
Then on every change:
```sh
./build.sh
```
That builds `linux/amd64,linux/arm64` and pushes `rg.nl-ams.scw.cloud/valinor/finrod:{latest, <git-short-sha>}`. Take note of the short SHA it prints — that's what you pin in valinor.
## Deploy
Cluster manifests live in `valinor/apps/finrod/` (bjw-s app-template, internal-only ingress at `finrod.jpnadas.xyz`). Merging a PR there triggers ArgoCD to sync; bumping the image tag in `values.yaml` is how you roll out a new build.
Cluster manifests live in `valinor/apps/finrod/` (bjw-s app-template, internal-only ingress at `finrod.jpnadas.xyz`). To roll out a new build:
1. `./build.sh` here — get the SHA
2. Bump `tag:` in `valinor/apps/finrod/values.yaml` to that SHA on a branch
3. Merge → ArgoCD syncs the new image
Using `:latest` works for the first deploy (the pull policy is `Always`) but pinning to a SHA on each rollout gives you trivial rollback via git revert.