1. Fix possible Autoload Bug by using ACPU optimization over Authoritative Classmap.

2. In Development, use the mounted `vendor` folder instead of having to reinstall everything when introducing a new package 📦
3. Move Composer's Post-Install, and Post-Autoload command to build time, added an entry to FAQ to how to fix build failure at post-install-cmd in most frameworks.

Author: sherifabdlnaby

Dockerfile

@@ -26,6 +26,7 @@ RUN apt-get update && apt-get -y --no-install-recommends install \
     tini=0.18.0-1               \
     libfcgi-bin=2.4.0-10        \
     libicu-dev=63.1-6+deb10u1   \
+    gettext-base                \
     # Needed for Application Runtime
 
     # Clean metadata and clear caches
@@ -125,7 +126,7 @@ RUN composer config platform.php ${PHP_VERSION}
 # Install Dependeinces
 ## * Platform requirments are checked at the later steps.
 ## * Scripts and Autoload are run at later steps.
-RUN composer install -n --no-progress --ignore-platform-reqs --no-plugins --no-scripts --no-autoloader --prefer-dist
+RUN composer install -n --no-progress --ignore-platform-reqs --no-plugins --no-scripts --no-dev --no-autoloader --prefer-dist
 
 # ======================================================================================================================
 # ==============================================  PRODUCTION IMAGE  ====================================================
@@ -143,10 +144,10 @@ COPY --chown=www-data:www-data --from=vendor /app/vendor /var/www/app/vendor
 COPY --chown=www-data:www-data . .
 
 # 1. Dump optimzed autoload for vendor and app classes.
-# 2. --no-scripts as scripts are run on runtime via entrypoint.
-# 3. checks that PHP and extensions versions match the platform requirements of the installed packages.
-RUN composer dump-autoload -n --optimize --no-scripts --no-dev --classmap-authoritative && \
+# 2. checks that PHP and extensions versions match the platform requirements of the installed packages.
+RUN composer dump-autoload -n --optimize --no-dev --apcu && \
     composer check-platform-reqs && \
+    composer run-script -n post-install-cmd && \
     post-build
 
 ENTRYPOINT ["entrypoint-prod"]
@@ -189,14 +190,6 @@ COPY docker/php/dev-*   $PHP_INI_DIR/conf.d/
 # Run as non-root
 USER www-data
 
-# Copy Vendor And Generate Autoload ( Needs Composer.* to check reqs and generate autoload)
-COPY --chown=www-data:www-data composer.json composer.json
-COPY --chown=www-data:www-data composer.lock composer.lock
-COPY --chown=www-data:www-data --from=vendor /app/vendor /var/www/app/vendor
-RUN composer install --no-scripts && composer dump-autoload -n --no-scripts && \
-    composer check-platform-reqs && \
-    post-build
-
 # Entrypoints
 ENTRYPOINT ["entrypoint-dev"]
 CMD ["php-fpm"]

README.md

@@ -206,6 +206,10 @@ In `docker/` directory there is `post-build` and `post-install` scripts that are
 2. Why `debian` based image not `alpine` ?
     
     1. While a smaller image is very desired, and PHP image is infamous of being big. Alpine lacks a lot of packages (Available via `apk`) that a typical PHP would need. Some packages are not even available for alpine as they link to glibc not musl.
+    2. The image is `alpine` compatible, even the entrypoint and helper scripts are `sh` compatible, modifying the image to use `alpine` variant is possible with minimal changes to the image, you'll need to install the same package you're already using but for `alpine` and using `apk`.  
+3. Image Build Fails as it try to connect to DB.
+    
+    - A typical application in most Frameworks comes with `Doctrine` ORM, Doctrine if not configured with a DB Version, will try to access the DB at php's script initialization (even at the post-install cmd's), and it will fail when it cannot connect to DB. Make sure you configure doctrine to avoid this extra DB Check connection.
 
 
 # License 

docker-compose.yml

@@ -11,7 +11,6 @@ services:
         COMPOSER_AUTH: "{}"
     restart: unless-stopped
     volumes:
-      - /var/www/app/vendor
       - .:/var/www/app
 
   web:

docker/entrypoints/entrypoint-base

@@ -1,31 +1,13 @@
 #!/bin/sh
 set -eu
 
-
-
 # --------------------------------------------------------------------------------------------------------------------
 
 # !-- We want to only print in logs if something wrong happened, hence how below code is written. --!
 
-# Run post-install-cmd (if exists)
-if (composer run-script -l 2> /dev/null | command grep --silent "post-install-cmd" > /dev/null)
-then
-    echo "► Running composer's post-install-cmd..."
-    output=$(composer run-script --no-interaction post-install-cmd 2>&1) || { echo "error running composer post-install-cmd script: $output"; exit 1; }
-    echo "✔ Successful"
-fi
-
-# Run post-autoload-dump (if exists)
-if (composer run-script -l 2> /dev/null | command grep --silent "post-autoload-dump" > /dev/null)
-then
-    echo "► Running composer's post-autoload-dump..."
-    output=$(composer run-script --no-interaction post-autoload-dump 2>&1) || { echo "error running composer post-autoload-dump script: $output"; exit 1; }
-    echo "✔ Successful"
-fi
-
 # Run custom ad-hoc pre-run script
 echo "► Running custom pre-run script..."
-output=$(pre-run 2>&1) || { echo "error running custom pre-run script: $output"; exit 1; }
+pre-run
 echo "✔ Successful"
 
 # ----------------------------------------------------------------------------------------------------------------------

docker/entrypoints/entrypoint-dev

@@ -3,6 +3,14 @@ set -eu
 
 # ----------------------------------------------------------------------------------------------------------------------
 
+echo "Checking if 'vendor' folder exists..."
+if [ -d "vendor" ]; then
+  echo "'Vendor' Folder exists, Skipping running Composer Install."
+  echo "To install new package, either run 'composer install' from inside the container via 'exec', or remove the vendor folder all together."
+else
+  echo "Vendor Folder does not exist, running composer install..."
+  composer install -n
+fi
 
 # Run Entrypoint and pass CMD to it (Don't forget exec)
 exec entrypoint-base "${@}"