Repository navigation
Add Docker Compose installation and Docker Hub publication - #9
Merged
Merged
Conversation
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.
Why
Installing CertLord currently requires separately provisioning Vault, Redis and Auton. Provide a documented single-host installation with protected APIs and persistent data.
Changes
Validation
Sphinx warnings-as-errors build and script syntax checks passed locally. Docker runtime validation runs in GitHub Actions because the local execution environment has no Docker engine. Existing full lifecycle and package gates remain enabled.
No source release tag is moved; CertLord runtime remains 1.0.0. Docker Hub publication requires DOCKERHUB_TOKEN in this repository.