Feature Request: Extending the Docker image with important PHP configuration values ​​via ENV

[csaeum]

👉 Describe the problem

I would like to configure the Docker image serversideup/php:8.3-fpm-apache (or a Shopware project based on it) with specific PHP values ​​that are recommended by Shopware or helpful for optimal performance and stability. Currently, it is not possible to set these values ​​directly via ENV variables when the container starts.

Example:
The official Shopware script recommends configuring:

• pm.status_path for FPM status monitoring
• max listen queue = 0 (see PHP documentation – max listen queue)
• opcache.enable_file_override=1
• zend.detect_unicode=0
• realpath_cache_ttl=3600

👥 Problem evidence & reach
I suspect I'm not the only one experiencing this issue – everyone who uses Shopware in conjunction with Docker and wants to implement recommendations from the Shopware Performance Guide or setup scripts is affected. Teams trying to properly automate CI/CD or cloud-native deployments are particularly affected.

🏆 How to solve this problem
It would be helpful if the image (or an upstream startup script) offered the option to set certain PHP INI values ​​via environment variables – e.g. E.g., via envsubst or template handling at container startup.

Detail 1 – Values ​​that should be set via ENV:

• FPM_PM_STATUS_PATH → writes pm.status_path
• PHP_OPCACHE_ENABLE_FILE_OVERRIDE=1
• PHP_ZEND_DETECT_UNICODE=0
• PHP_REALPATH_CACHE_TTL=3600
• PHP_FPM_LISTEN_BACKLOG=0 (for listen.backlog in FPM)

Detail 2 – Optional implementation approaches:

• Preparing your own php.ini or www.conf file via envsubst at runtime
• Configuration via mount (/etc/php/conf.d/custom.ini)
• Documentation of the supported ENV variables in the Docker Hub or GitHub repo

🥰 Describe the "impact" on users?

This would make the Docker image much more flexible to use – especially in automated DevOps/cloud environments where manually accessing containers and editing configuration files is impractical. It increases performance and prevents errors in production (e.g., regarding the file_exists() cache or Unicode detection).
💯 How do we validate the problem is solved?

As soon as it is possible to set the mentioned PHP configuration values ​​without manual configuration in the container (e.g., using simple ENV variables in docker-compose.yml), the problem is solved.

  app:
    image: serversideup/php:8.3-fpm-apache
    environment:
      - PHP_REALPATH_CACHE_TTL=3600
      - PHP_OPCACHE_ENABLE_FILE_OVERRIDE=1
      - FPM_PM_STATUS_PATH=/fpm-status```