Repository navigation
spear-image: get/update lifecycle verbs for base and project - #14
Merged
Merged
Conversation
`get <base|project>` fetches a tier's image without the caller knowing where it lives -- the registry (SPEAR_REGISTRY_IMAGE) first, else a shared tarball directory (SPEAR_SHARE_DIR, spear-<tier>-<version>.tar.zst). `update <base|project>` rebuilds from local.conf, refreshes that tarball and tries to push; re-indexing stays a separate, deliberate step. Both are option-free -- client/local.conf holds every setting. Document the two verbs and the two new settings in docker/README.md, the container chapter and local.conf.example.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two option-free lifecycle verbs over
spear-image build, so neither a maintainer nor a colleague has to remember where a tiered image lives or which flags built it. Everything comes fromclient/local.conf.get <base|project>— fetch a tier's image: the registry (SPEAR_REGISTRY_IMAGE) first, else a shared tarball directory (SPEAR_SHARE_DIR,spear-<tier>-<version>.tar.zst). Idempotent; an image already present is left alone.update <base|project>— rebuild fromlocal.conf, refresh that tarball, and try to push. Rebuild only: re-indexing a corpus stays a separate, deliberate step.update basebuilds the harness first if missing;update projectrequires the base.Two new
local.confsettings say where images travel:SPEAR_REGISTRY_IMAGE(full repo path) andSPEAR_SHARE_DIR(shared tarball dir, default the tree's parent).Documented in
docker/README.md(colleague-facing), the container chapter, andlocal.conf.example.