fix(containers): switch VeriSimDB to pre-built GHCR image#28
Merged
Conversation
Both compose files were broken on fresh clone because VeriSimDB was referenced as a local build context (../../nextgen-databases/verisimdb) that is never present in a burble checkout. Replace the build stanza with a pull from ghcr.io/hyperpolymath/verisimdb:latest in both compose.toml and selur-compose.toml. Add publish-verisimdb.yml to build and push the image from hyperpolymath/nextgen-databases on a weekly schedule and on manual dispatch, so the registry image stays fresh without requiring end-users to have the VeriSimDB source. Closes #27 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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
1 participant
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.
Summary
build = { context = "../../nextgen-databases/verisimdb" }stanza in bothcompose.tomlandselur-compose.tomlwithimage = "ghcr.io/hyperpolymath/verisimdb:latest"— the sibling-directory path is never present on a fresh clone, so the stack could not start at all.github/workflows/publish-verisimdb.ymlto build VeriSimDB fromhyperpolymath/nextgen-databasesand push to GHCR on a weekly schedule and onworkflow_dispatch; all actions are SHA-pinned per workflow-linter policyCloses #27
Test plan
podman-compose -f containers/selur-compose.toml up -dsucceeds on a fresh clone (once the image exists on GHCR)podman-compose -f containers/compose.toml uplikewise succeedsghcr.io/hyperpolymath/verisimdbnextgen-databasesis private, setNEXTGEN_DATABASES_TOKENrepo secret (PAT withreporead scope) before triggering the publish workflowNotes
The publish workflow falls back to
GITHUB_TOKENfor public repos. SetNEXTGEN_DATABASES_TOKENifnextgen-databasesis private.🤖 Generated with Claude Code