Felix Faerber
67b00b8848
Docker / build (pull_request) Successful in 23s
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.