homelab-frontend

Author	SHA1	Message	Date
Admin Bot	71090323f3	fix: use env vars for docker registry credentials Pass FORGEJO_REGISTRY_USER and FORGEJO_REGISTRY_TOKEN via environment variables. Image: forgejo.riotpiao.com/rock/api-gateway (API gateway service)	2026-09-07 00:17:06 -07:00
Admin Bot	ace091068e	fix: validate registry credentials before docker login Add credential validation step to catch missing secrets early with clear error message. Use direct secret injection (not env vars) for better security. Isolate docker config to /tmp/docker-config.	2026-09-07 00:17:06 -07:00
Admin Bot	f151bfe11e	fix: standardize CI workflow to unified pattern Reference: riotpiao.com action run 496/707 Unified structure: - test job: all branches + PRs - build-push job: main push only, depends on test - Install Node.js before checkout - Install docker only in build-push - Proper secrets and env handling - Docker login + build + push + prune	2026-09-07 00:17:06 -07:00
rockandAdmin Bot	736c0d7724	fix: use env vars for docker registry credentials (#2 ) CI / Test (push) Successful in 1m51s Details CI / Build & Push Image (push) Failing after 1m6s Details Fix registry login by passing FORGEJO_REGISTRY_USER and FORGEJO_REGISTRY_TOKEN via environment variables instead of direct secret interpolation. Uses the proven pattern from riotpiao.com reference commit. This prevents credentials from being exposed in logs or shell history while keeping the standard docker login approach. After merge + org-level secrets configured: - All repos inherit FORGEJO_REGISTRY_USER and FORGEJO_REGISTRY_TOKEN - CI validates credentials exist before docker login - Image pushed to registry on main push --------- Co-authored-by: Admin Bot <[email protected]> Reviewed-on: #2	2026-09-07 06:50:48 +00:00

Compare commits

Diff Content Not Available