Add a short high-level explanation of typical docker-compose use cases #13477
+9
−0
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.
This pull request adds a short, high-level documentation section explaining typical use cases for docker-compose.
While docker-compose is widely used, the documentation currently focuses very quickly on configuration details without clearly outlining when docker-compose is a good fit and when other tools may be more appropriate.
The added section provides a concise overview of common scenarios such as local development, testing, and small setups, and briefly contrasts these with use cases where plain Docker commands or Kubernetes might be better suited.
This change is documentation-only and does not introduce any new features or configuration changes.
Definition of Done (DoD):
Related issue: #13476