Answer architecture round 2: 0 🔴, 0 🟡; tie the token choice to the account type, and keep GHCR's reason in the registry decision

This commit is contained in:
2026-10-14 11:19:30 +02:00
committed by Lillem4n
parent 508e93d11a
commit fbadb99634
2 changed files with 10 additions and 7 deletions
+7 -5
View File
@@ -982,8 +982,10 @@ Valid while GitHub hosts the code.
2026-10-14, decided by the maintainer. Serves goal 1.1; technical principle: prefer the
vendor-neutral option (`~/.claude/principles/technical-principles.md`). Docker Hub is
Docker's default registry, so `docker run larvit/fejkdata` works with no host in the name;
that is a capability only Docker Hub has. GHCR stays the image's source: GoReleaser pushes
there, and a job of its own copies the image to Docker Hub, so a Docker Hub failure holds up
no other channel. GHCR also serves CI on shared runners, which Docker Hub's per-IP limit on
anonymous pulls blocks. Leaving Docker Hub costs each user an edit of every `docker run` line
and pinned script that names the bare `larvit/fejkdata`.
that is a capability only Docker Hub has. GHCR stays the image's source, and adds no
vendor while GitHub hosts the code; being OCI, the image moves to another registry by a
change of path. GoReleaser pushes there, and a job of its own copies the image to Docker
Hub, so a Docker Hub failure holds up no other channel. GHCR also serves CI on shared
runners, which Docker Hub's per-IP limit on anonymous pulls blocks. Leaving Docker Hub
costs each user an edit of every `docker run` line and pinned script that names the bare
`larvit/fejkdata`.