Skip to content

Separate registry access from template publishing - #28

Merged
czpython merged 1 commit into
mainfrom
codex/shared-template-registry
Oct 3, 2026
Merged

czpython merged 1 commit into
mainfrom
codex/shared-template-registry

Conversation

@czpython

@czpython czpython commented Sep 5, 2026 •

Copy link
Copy Markdown
Owner

Registry credentials become service settings. REGISTRY_HOST, REGISTRY_USERNAME, and REGISTRY_PASSWORD give access to private images on one registry host. TEMPLATE_REPOSITORY names the repository path on that host where drukbox publishes template images. Registry access works without a template repository.

The credentials go only with an image on the registry host. The exe provider passes them to exe.dev with the host image. The docker provider uses them when the Docker engine pulls a host image that it does not have.

Each provider that builds templates publishes them to the template repository. exe boots hosts from a registry, so its templates require the repository. docker and docker-sbx publish when it is set and keep the image local when it is not.

These settings replace EXE_IMAGE_REGISTRY, EXE_REGISTRY_USERNAME, and EXE_REGISTRY_PASSWORD. Split the old repository value into its host and its path. A template repository without complete registry access stops the service at start.

Template image names and the API are unchanged.

Druks consumer: czpython/druks#811

@czpython
czpython force-pushed the codex/shared-template-registry branch from f2b0df5 to c5c45c1 Compare October 3, 2026 08:22
@czpython
czpython marked this pull request as ready for review October 3, 2026 08:24
@czpython
czpython merged commit 623442d into main Oct 3, 2026
6 checks passed
@czpython
czpython deleted the codex/shared-template-registry branch October 3, 2026 08:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant