Closed dacgray closed 5 years ago
hmm at least one docker-compose file is required to exist
makes sense.
it actually solves the requirement of
"environments": {
"dev": {
"file": "./docker-compose.yml"
},
"prod": {
"file": "./docker-compose.prod.yml"
}
},
because we can have docker-compose.local.yml
to do what each environment specific file would do
yep, I'll close this.
After discussion and an agreement of standards at https://github.com/crazyfactory/standards/blob/master/docker.md this is no longer a problem.
Relevance
With this pattern:
When running
dopr start:prod
on prod we get:dopr forces us to define the dev environment vars we only use in docker-compose.yml in production.
The workaround is therefore to use
docker-compose -f ...
instead ofdopr -env production up -d
Proposal
Allow no file defined if we define environments:
Right now this pattern gives us:
at least one docker-compose file is required to exist