3 Commits

Include renames

Author	SHA1	Message	Date
Felix FaerberandClaude Opus 5	70786f73ab	push with a write:package token, not the Actions token ... Second build failed the same way: docker login to this instance's registry returns "unauthorized" for the automatic Actions token, and declaring permissions: packages: write did not change it -- Gitea's task token is accepted by the API but not by the package registry. So the push uses REGISTRY_TOKEN, an org secret holding a personal access token scoped to write:package and nothing else. The step fails with that sentence in the log rather than another bare "unauthorized", because the difference between a missing secret and a rejected credential is not visible from the error docker prints. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CYFnHida4AdiNDek2pzgXx	2026-09-15 12:38:14 +03:00
Felix FaerberandClaude Opus 5	f2f3e4e3f9	declare packages: write so the registry login works ... The first build pushed nothing: `docker login git.ffaerber.duckdns.org` came back "unauthorized". Gitea scopes the automatic Actions token from the job's permissions block, and without one it has no package write -- so the build succeeded and the push failed on auth, which reads like a credential problem rather than a missing declaration. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CYFnHida4AdiNDek2pzgXx	2026-09-15 12:36:51 +03:00
Felix Faerber	67b00b8848	build on Gitea, against the homelab API ... Same move as the gateway repo -- build on the homelab runner, push to this Gitea's registry, no deploy step -- with one difference that matters more here than anywhere else. Vite inlines import.meta.env at BUILD time. VITE_API_URL is therefore baked into the bundle, and the GitHub build bakes https://api.t4t-gateway.com. Running that image on the homelab would put a UI at t4tgw.ffaerber.duckdns.org that talks to the VPS: a test signup would create a real account on production, and the two instances would look identical while being the same instance. This build bakes the homelab API, which is what makes running them side by side mean anything. The app also falls back to the production URL when the variable is missing (app/routes/*.tsx), so an unset build arg fails the same way silently. It is set explicitly in the workflow env rather than left to a default. .github/workflows is removed from this copy so Gitea does not try to run the GitHub one; the GitHub repository keeps its own.	2026-09-15 12:30:27 +03:00