Help to understand the workflow about symfony-docker HOT 2 CLOSED

Hi,
thank you so much for your answer and for your detailed explanation. It's really useful and i will try now to understand all of this and run the code step by step :)
Thanks a lot for your time and for sharing your knowledge.

from symfony-docker.

Hello, thanks for your word 😃

For how entrypoint works, i recommend you to look at the definition and example here : https://docs.docker.com/engine/reference/builder/#understand-how-cmd-and-entrypoint-interact

And next :

1. We install Flex as a global dependency like this every command composer in the container even outside the project benefits of the parallale downloader.
2. The skeleton at this level allows you to initialize a new project with the latest stable version if you have not started or will be overwritten by the COPY, to cache it in the docker layers and to use it to initialize the volume inside the container. (the last two can be useful for publishing the image and manage it with a orchestrator in production)
3. For this point, I'm not sure (I haven't studied the problem more closely at the begining), but I think with docker-compose in dev mode the volume is reset with you host (docker-compose line 18) at the first mounting, so if you don't started a project we create the skeleton dynamically to prevent errors with ACLs with var folder. (because your host don't have any symfony project yet)

The main link between stage 2 & 3 is for the project to work as well as in development or for production.

Note: By writing these lines, I realize that it would be useful to have the composer install after the COPY in the dockerfile to use the docker cache as much as possible for production 🤔

from symfony-docker.