Refine Docker Compose Usage in Documentation #7290
Draft
+5
−9
Conversation
This file contains 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
This was referenced May 17, 2024
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.
This PR complements #6924 / #692. In addition to update syntax/naming conventions, this takes a step further by enhancing Docker Compose usage throughout the documentation and examples.
Summary of Changes
Removal of Deprecated
versionField:versionfield from examples as it is deprecated and was used inaccurately in most cases.Simplification by Removing Unnecessary
links:linksfield at the service level is unnecessary and has no effect in the examples. Removing it simplifies the examples.Update to Volume Mounts:
:cachedsuffix from volume mounts, which is specific to Mac and is now unnecessary. This keeps the examples platform-agnostic and simpler.