30
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 26 Sep 2024
30 points (96.9% liked)
Programmer Humor
19623 readers
1 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 1 year ago
MODERATORS
Simpler to keep everything in one compose file if you can, under a
testservice that doesn't build unless explicitly namedUn-weird that env var and use the normal, boring feature of defining
environmentunder yourtestserviceThe variable is already in the environment, it just doesn’t have a default because it’s required for each container
You can reference envs from the host in docker compose, so code it in instead of manually passing tribal knowledge in: https://stackoverflow.com/a/73826410
Yep, you can also set defaults, required, alternates, etc
This discussion did help me realize that my problem was that I forgot an
!overrideon one of my service’s options. Now it’s just merging the two compose files and setting the profile, thanks for that!