Repository navigation
Publish Docker image on release; move certs to runtime - #3
Merged
Merged
Conversation
Add a release workflow that builds and pushes the image to GHCR when a GitHub release is published from a commit on main. Stop baking TLS certs into the public image; users mount their own at runtime. Add Dockerfile.local (make docker-local) for local-only images with creds.yaml and certs/ baked in, and document both in the README. Co-Authored-By: Claude Opus 5.5 (1M context) <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
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.
Add a release workflow that builds and pushes the image to GHCR when a GitHub release is published from a commit on main.
Stop baking TLS certs into the public image; users mount their own at runtime. Add Dockerfile.local (make docker-local) for local-only images with creds.yaml and certs/ baked in, and document both in the README.