clarify docker-compose environment format (#91) #92
Conversation
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
Signed-off-by: eternal-flame-AD <[email protected]>
eternal-flame-AD
force-pushed
the
compose-env-spec
branch
from
2d9ff24 to
33056f8
Compare
jmattheis
reviewed
Nov 21, 2024
Signed-off-by: eternal-flame-AD <[email protected]>
jmattheis
approved these changes
Nov 22, 2024
Member
Author
|
Seems like it is refusing to deploy because admin does not have escape characters in it. Is this lint really useful that you should prefer double quotes in YAML (I never do it and I think most people use single quotes unless they need \r \n to work |
Member
|
I fixed the prettier stuff in a newer commit, it had single quotes configured but the file was in the wrong directory. |
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.
Fixes #91