Repository navigation
feat: deploy folder with compose example, drop helm chart - #18
Merged
Merged
Conversation
The chart only served one cluster and its README carried that setup's details. deploy/ now holds a single-instance compose stack from the published image (migration before server, persistent volumes, loopback port), .env.example, and a README covering reverse proxy, upgrades, backups and multi-replica requirements. BREAKING CHANGE: deploy/chart and the root docker-compose.yaml are removed; use deploy/docker-compose.yaml or your own manifests.
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.
Master counterpart of #17.
Moves deployment docs and examples into
deploy/and drops the in-repo Helm chart.deploy/docker-compose.yaml: single instance from the published image. A one-shot migration runs before the server; Postgres and Redis keep their data in named volumes; the server is published on loopback with a/readyzhealthcheck.deploy/.env.example: every setting, with placeholders.deploy/README.md: compose guide (reverse proxy andX-Real-IP, upgrades, backup/restore) and notes for multi-replica deployments.deploy/. The stale Kustomize/Argo CD section is removed.deploy/chartand the rootdocker-compose.yamlare removed. Breaking for anyone deploying from the chart.Smoke-tested from a fresh
.env: migration ran,/readyzreturned 200, data surviveddown/up, and the backup/restore commands in the README worked. Published images are linux/amd64 only, so compose pins the platform.