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
Currently a check is made against version.php to see if if the current container is newer than the installed version, and if not, application files are copied into a volume. This is inefficient, and bad practice.
In the case of running the apache version, there is no reason to do this; it only serves to waste space on the volume store, and slow install/upgrade times.
In the case of running the fpm version, this is still a hack; files required by the nginix/lighttpd servers should be copied in manually (replicate the old behavior in an init container), or via docker's behavior when mounting a volume on a directory. The better solution would be to create a new image that runs a pre-configured/configurable nginx bassed off of this image -- any required configs could then be shared in a volume.
The text was updated successfully, but these errors were encountered:
Currently a check is made against
version.php
to see if if the current container is newer than the installed version, and if not, application files are copied into a volume. This is inefficient, and bad practice.In the case of running the
apache
version, there is no reason to do this; it only serves to waste space on the volume store, and slow install/upgrade times.In the case of running the
fpm
version, this is still a hack; files required by the nginix/lighttpd servers should be copied in manually (replicate the old behavior in an init container), or via docker's behavior when mounting a volume on a directory. The better solution would be to create a new image that runs a pre-configured/configurable nginx bassed off of this image -- any required configs could then be shared in a volume.The text was updated successfully, but these errors were encountered: