Skip to content
Devilbox

Enable and configure PHP Community

Enable and configure PHP Community

PHP Community replaces the default Devilbox PHP-FPM image with a community flavour while keeping the same php service, mounts, and network identity.

How it works

Devilbox keeps optional integrations as override snippets in the compose/ directory. To enable PHP Community, copy its snippet into the project root as docker-compose.override.yml, then start the stack.

Enable

Terminal window
cp compose/docker-compose.override.yml-php-community docker-compose.override.yml
./dvl.sh up

Configuration

The snippet overrides the existing php service image:

image: devilbox/php-fpm-community:${PHP_SERVER}-${PHP_COMMUNITY_FLAVOUR:-devilbox}

It uses the same service name, hostname, ports, volumes, and IP address as the standard PHP service. Configure it with existing PHP settings plus:

VariableDefaultPurpose
PHP_SERVERfrom your .envPHP version tag used by the PHP service.
PHP_COMMUNITY_FLAVOURdevilboxCommunity image flavour suffix.

Example .env entries:

Terminal window
PHP_SERVER=8.3
PHP_COMMUNITY_FLAVOUR=devilbox

Usage

Start the stack and confirm the PHP image:

Terminal window
./dvl.sh up
docker compose ps php

Check the active PHP version from inside the container:

Terminal window
./dvl.sh exec php -v

Use the same project workflow as the standard PHP container:

Terminal window
./dvl.sh shell
composer install

Disable

Terminal window
./dvl.sh down
rm docker-compose.override.yml
./dvl.sh up

Troubleshooting

  • If Docker cannot pull the image, verify the combination of PHP_SERVER and PHP_COMMUNITY_FLAVOUR exists.
  • If PHP still uses the old image, recreate the service with ./dvl.sh down before starting it again.
  • If extensions differ from the standard image, review PHP_MODULES_ENABLE and PHP_MODULES_DISABLE in .env.

See also