compose: factor services into separate files - #2395
Merged
Merged
Conversation
kkovaacs
approved these changes
Jul 29, 2026
kkovaacs
left a comment
kkovaacs
left a comment
Collaborator
There was a problem hiding this comment.
Looks good to me!
It'd be great if we could use the missing pull policy though, but that's just a nit at this point.
Mirko-von-Leipzig
changed the title
Mirko-von-Leipzig
force-pushed
the
mirko/split-compose
branch
from
July 29, 2026 14:01
c13ce61 to
7e039b9
Compare
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
2 participants
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
This PR splits our docker compose file into separate files per service. This is in anticipation of adding more services, making a single file impractical.
The files are included in the main file, this means users don't have to manually
-f <file>. The downside of this approach is thatdocker compose publishdoes not support this split. We circumvent this by flattening the files before publishing in the release flow. This is abstracted by a github action, so its not very painful.Changelog