Repository navigation
[Repo] ci: Validate compose files; document updates and backups - #72
Merged
Merged
Conversation
Runs docker compose config for every service with its .env.example, and checks that each service folder holds exactly docker-compose.yml, .env.example and README.md. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 59 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. |
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.
Summary
Three repo-wide improvements:
.github/workflows/validate-compose.yml)docker compose -f <service>/docker-compose.yml config -qforevery service, with that service's
.env.exampleas--env-file..env.exampleon purpose (so the deployfails until they are set, e.g. Garage secrets,
ARCHISTEAMFARM_CRYPTKEY)get a dummy value in CI only, so
${VAR:?msg}resolves.cloudflaredjoinsdokploy-network, which Dokploy provides ondeploy but the compose file does not declare. CI adds a small
override declaring it as external, for validation only; the compose
files are unchanged.
exactly
docker-compose.yml,.env.exampleandREADME.md.actions/checkoutpinned by commit SHA,permissions: contents: read.## Updatessection at the end of every service README: whichcontainers Watchtower updates and the tag they follow, what is pinned
and bumped by hand (qBittorrent, VueTorrent) or by Dependabot (Garage),
and the Dokploy watch path (
<service>/**). MongoDB in MySpotifyfollows
8, so a new major is a manual change with a dump/restore.Garage and Watchtower already had the section; it was extended.
backups are Dokploy backups to S3-compatible storage configured outside
this repository.
Test plan
config -qpasses for all 14services and the 3-file check passes.
npx markdownlint-cli2 "**/*.md"passes.Validate Composeworkflow passes on this PR.🤖 Generated with Claude Code