Repository navigation
Publish image to GHCR, mirroring finance-agent's packaging - #8
Merged
Merged
Conversation
setup.sh/README updates both run docker compose up -d --build, which rebuilds from source on the CasaOS box every time. finance-agent already solved this the same way this project needed to: build once in CI and let the host pull. - .github/workflows/docker.yml builds and pushes ghcr.io/agb1986/ai-data-store on every push to main, ported from finance-agent's workflow of the same name - docker-compose.yml's api/web services keep build: . as a local-dev fallback but now also carry the GHCR image: tag, so docker compose pull works once the workflow has published at least one image - README documents docker compose pull as the update path on CasaOS, alongside the existing build path Co-Authored-By: Claude Sonnet 5 <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
.github/workflows/docker.yml— builds and pushesghcr.io/agb1986/ai-data-store(:latestand:<sha>) on every push tomain, ported directly from finance-agent's workflow of the same name (same login/buildx/build-push-action steps, GHA layer caching).docker-compose.yml—api/webservices now carry bothbuild: .(unchanged, so a fresh clone still works with no registry access) andimage: ghcr.io/agb1986/ai-data-store:latest. This mirrors finance-agent's own compose file, which keeps the same dualbuild:/image:pair for the same reason:docker compose up --buildstill works locally, whiledocker compose pullnow fetches the prebuilt image instead of rebuilding on the CasaOS host.docker compose pull && docker compose up -das the update path, alongside the existinggit pull && docker compose up -d --build, worded the same way as finance-agent'sdocs/deployment.md.Today
setup.shand the README's update instructions only ever rebuild locally on the CasaOS box. This closes that gap the same way finance-agent already did.Test plan
docker compose config -q— compose file parses and resolvesyaml.safe_load)ruff check ./pytest— unaffected, still 57 passed (no Python changed)docker.ymlworkflow runs and publishes toghcr.io/agb1986/ai-data-storedocker compose pull && docker compose up -dpicks up the published image🤖 Generated with Claude Code