Remove the old example compose files that only made sense for submodules#25
Merged
Conversation
with a monorepo, it makes more sense to have the top level compose be the one source of truth. People wishing to build/test parts of the project can use the top level compose by just specifying the name(s) of the containers they wish to build/run. People wishing to reuse parts of the code can simply take relevents snippets from the top level compose.
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.
with a monorepo, it makes more sense to have the top level compose be the one source of truth. People wishing to build/test parts of the project can use the top level compose by just specifying the name(s) of the containers they wish to build/run. People wishing to reuse parts of the code can simply take relevents snippets from the top level compose.