fix: use env vars for docker registry credentials #4

Merged

rock merged 4 commits from fix/registry-login-env into main 2026-09-07 06:48:28 +00:00

Conversation 0 Commits 4 Files Changed 1

+15 -6

4 Commits

Author	SHA1	Message	Date
Test	984e6f5d6e	fix: use env vars for docker registry credentials ... Pass FORGEJO_REGISTRY_USER and FORGEJO_REGISTRY_TOKEN via environment variables instead of direct secret interpolation. This is the standard approach used across all repos and prevents credentials from being exposed in logs or shell history. Fixes registry login failures by using the proven pattern.	2026-09-06 23:40:46 -07:00
Test	101ba70b57	fix: use env vars for docker registry credentials ... Pass FORGEJO_REGISTRY_USER and FORGEJO_REGISTRY_TOKEN via environment variables instead of direct secret interpolation. This is the standard approach used across all repos and prevents credentials from being exposed in logs or shell history. Fixes registry login failures by using the proven pattern from riotpiao.com.	2026-09-06 23:37:51 -07:00
Test	b0a8e4bd5c	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-06 23:35:02 -07:00
Test	3d1360a135	fix: standardize poimen-workflows CI to unified pattern ... Unified pattern enforced: - test job: runs on all branches + PRs - build-push job: only on main push, depends on test - Proper env vars (GOPRIVATE, REGISTRY, IMAGE) - Install Node.js before checkout - Install docker only in build-push - Docker login + build + push + prune	2026-09-06 23:17:10 -07:00