You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I try to containerize my own project I have to store in a different place the php-fpm.ini that is inside the php folder , delete the index.php, copy my code into the php folder and add back the php-fpm.ini, I feel like the structure should be more like:
root
--- php
--- php-fpm.ini
--- webapp
--- index.php (or the files of the project to be containerized)
In this structure we keep the php config files in a different location than the php code files.
so that in the Dockerfiles we can copy all the files inside the project folder, so instead of
COPY php/index.php /var/www/html/index.php
we can do something like
COPY ./php/. /var/www/html/
to copy all the files
The text was updated successfully, but these errors were encountered:
oh actually that is just the path for lemp stack not the application source code. the index.php is just a default landing page to show "it works". the actual app should instead directly volume map to /var/www/html. hope this helps. :)
@adhocore oh got it, the way I use this project is: I clone the project put the code of my project in the PHP folder and then build the docker image then I distribute the image to the frontend devs or submit it to Google cloud to deploy it into an instance for the QA team, I know maybe this isn't the intention of the repo but it has been working for us.
When I try to containerize my own project I have to store in a different place the
php-fpm.ini
that is inside thephp
folder , delete the index.php, copy my code into the php folder and add back thephp-fpm.ini
, I feel like the structure should be more like:In this structure we keep the php config files in a different location than the php code files.
so that in the Dockerfiles we can copy all the files inside the project folder, so instead of
we can do something like
to copy all the files
The text was updated successfully, but these errors were encountered: