feat: rework compose config to be more modular#103
Open
jippi wants to merge 31 commits into
Open
Conversation
3c1a0a3 to
80942f4
Compare
80942f4 to
4db9a9d
Compare
This was referenced Jan 25, 2025
… key on the include
[skip-ci]
…xelfed into rework-compose-config-v2
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
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.
Context
compose.default.yamlis what the end-user would see by defaultcompose.yamlis now untracked by git (so owned by the server owner)docker compose configto get the generated configuration from the includes and paste it into their Portainer UIChanges
compose.default.yamlcontaining the default file folks will copy during setupincludeto tweak the configuration, includingportsto the hostdocker compose buildconfiguration_PROFILEenv keys to disable services, since you can just NOT include them nowcompose.yamlfileincludeversions do not match their preferences