docker-compose-prod.yml vs docker-compose.prod.yml about djangoforprofessionals

[wsvincent]

Hi @SPH73,

I'm late in response but...

• heroku.yml is needed for Docker images within Heroku https://devcenter.heroku.com/articles/build-docker-images-heroku-yml. It is Heroku-specific. The docker-compose-prod.yml file works for all Docker containers.
• I understand your confusion around how the ENVs are copied over. You can either use the -f flag to force usage of the prod yml file or do what we did in the book which is use docker-compose-prod.yml to test production locally and then manually update the env vars within Heroku.

Thanks for your question.

[SPH73]

Hi William, Thank you for responding. I will make a note of this within my project README doc. I will need to update this project at some point and it will be good to have a reference then. Best regards, Sue

…

On 16 May 2022, at 16:32, William Vincent ***@***.***> wrote: Hi @SPH73 <https://github.com/SPH73>, I'm late in response but... heroku.yml is needed for Docker images within Heroku https://devcenter.heroku.com/articles/build-docker-images-heroku-yml <https://devcenter.heroku.com/articles/build-docker-images-heroku-yml>. It is Heroku-specific. The docker-compose-prod.yml file works for all Docker containers. I understand your confusion around how the ENVs are copied over. You can either use the -f flag <https://docs.docker.com/compose/production/> to force usage of the prod yml file or do what we did in the book which is use docker-compose-prod.yml to test production locally and then manually update the env vars within Heroku. Thanks for your question. — Reply to this email directly, view it on GitHub <#73 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALOTHF4CBN7E5O5PZEKG64TVKJTBLANCNFSM4VECUL4Q>. You are receiving this because you were mentioned.