Gamma@beehaw.org to Programmer Humor@programming.devEnglish · 4 months agoModern self-inflicted problems require modern solutionsbeehaw.orgimagemessage-square14fedilinkarrow-up11arrow-down10
arrow-up11arrow-down1imageModern self-inflicted problems require modern solutionsbeehaw.orgGamma@beehaw.org to Programmer Humor@programming.devEnglish · 4 months agomessage-square14fedilink
minus-squareKache@lemm.eelinkfedilinkarrow-up0·edit-24 months agoSimpler 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
minus-squareGamma@beehaw.orgOPlinkfedilinkEnglisharrow-up0·4 months agoThe variable is already in the environment, it just doesn’t have a default because it’s required for each container
minus-squareKache@lemm.eelinkfedilinkarrow-up0·4 months agoYou 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
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