Skip to content

feat: rework compose config to be more modular#103

Open
jippi wants to merge 31 commits into
mainfrom
rework-compose-config-v2
Open

feat: rework compose config to be more modular#103
jippi wants to merge 31 commits into
mainfrom
rework-compose-config-v2

Conversation

@jippi

@jippi jippi commented Jan 18, 2025

Copy link
Copy Markdown
Owner

Context

  • compose.default.yaml is what the end-user would see by default
  • compose.yaml is now untracked by git (so owned by the server owner)
  • Folks using Portainer etc. can use docker compose config to get the generated configuration from the includes and paste it into their Portainer UI

Changes

  • Ship a compose.default.yaml containing the default file folks will copy during setup
  • Use granular include to tweak the configuration, including
    • Adding/removing each individual service
      • Proxy / Proxy ACME
      • Web
      • Cron
      • Worker
      • DB
      • Redis
    • Wether each service should expose its ports to the host
    • Wether each service should have a static container name
    • Wether each service should have docker compose build configuration
    • Wether each service should have dependency on other containers health
  • Remove _PROFILE env keys to disable services, since you can just NOT include them now
  • Easy off-ramp/customization since end-user own the compose.yaml file
    • Adding new services
    • Implement their own service configuration if the include versions do not match their preferences

@jippi jippi self-assigned this Jan 18, 2025
@jippi jippi force-pushed the rework-compose-config-v2 branch 7 times, most recently from 3c1a0a3 to 80942f4 Compare January 18, 2025 21:09
@jippi jippi marked this pull request as ready for review January 31, 2025 14:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant