this post was submitted on 26 Sep 2024
30 points (96.9% liked)

Programmer Humor

19488 readers
1147 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

founded 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 1 month ago* (last edited 1 month ago) (1 children)

Simpler to keep everything in one compose file if you can, under a test service that doesn't build unless explicitly named

Un-weird that env var and use the normal, boring feature of defining environment under your test service

[–] [email protected] 1 points 1 month ago (1 children)

The variable is already in the environment, it just doesn’t have a default because it’s required for each container

[–] [email protected] 1 points 1 month ago (1 children)

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

[–] [email protected] 1 points 1 month ago* (last edited 1 month ago)

Yep, you can also set defaults, required, alternates, etc

This discussion did help me realize that my problem was that I forgot an !override on one of my service’s options. Now it’s just merging the two compose files and setting the profile, thanks for that!