Skip to content

PHP stack containers


New Apache image

Since Drupal stacks 5.2.0+ Apache image wodby/php-apache has been replaced with wodby/apache with $APACHE_VHOST_PRESET=php

Restarting apache as default user:

sudo httpd -k restart

See details about virtual host preset.


See AthenaPDF stack documentation.


You can profile your application via by following the next steps:

  • Enable blackfire probe extension by adding the environment variable PHP_BLACKFIRE=1 to PHP container
  • Enable blackfire agent service in your stack
  • Add environment variables BLACKFIRE_SERVER_ID and BLACKFIRE_SERVER_TOKEN to blackfire agent service with appropriate values from your profile
  • Add environment variables BLACKFIRE_CLIENT_ID and BLACKFIRE_CLIENT_TOKEN to PHP service with appropriate values from your profile
  • Install blackfire companion extension for Chrome or Firefox
  • Start profiling your app via the extension and see data from dashboard

Fore more details please refer to the blackfire official documentation


A duplicate of the main PHP container runs with crond (instead of FPM). You can customize crontab from [Instance] > Stack > Settings page.


If Mailhog service enabled and chosen as Mail delivery service at [Instance] > Stack > Settings all outbound email will be caught by the Mailhog. You can view and release these emails from Mailhog UI, the URL can be found from Domains tab. When release specify opensmtpd in SMTP server field if you want to release emails to the default Mail transfer agent (OpenSMTPD).


See MariaDB stack documentation.


You can check the status of memcached and its hits by running the following command.

watch "echo stats | nc 11211"


Do not gzip pages in your PHP application

We already gzip content on Nginx side and it works faster. Having double gzip may cause issues.

Restarting nginx as default user:

sudo nginx -s reload

Custom config

If the default config and available environment variables are not enough for your customizations you can replace the config with your own:

  1. Copy /etc/nginx/conf.d/php.conf to your codebase, adjust to your needs
  2. Deploy code with your config file
  3. Add new environment variable NGINX_CONF_INCLUDE for nginx service, the value should the path to your *.conf file (e.g. /var/www/html/nginx.conf)

Mod pagespeed

Nginx comes with mod_pagespeed which is disabled by default. To enable it add NGINX_PAGESPEED=on environment variable to Nginx service.


Light-weight node.js container to help you build your application's frontend. The containers comes without any global pre-installed packages, you can add them by running yarn global add PACKAGE or by running yarn in a directory with your package.json file.


See OpenSMTPD stack documentation.


  • PHP can be configured with the following environment variables
  • Available php extensions
  • Composer pre-installed with a default global package hirak/prestissimo:^0.3 to download dependencies in parallel

Environment variables

Variables availability

Environment variables provided by Wodby are always available in PHP even if PHP_FPM_CLEAR_ENV set to no.

In addition to global environment variables, we provide the following variables in PHP container that you can use in your post-deployment scripts or settings files:

Variable Description
$APP_ROOT /var/www/html by default
$HTTP_ROOT e.g. /var/www/html/web
$CONF_DIR /var/www/conf by default
$WODBY_HOSTS [ "", "" ]

Deprecated variables:

Variable Instead use

Files directory permissions

Public files directory (symlink to /mnt/files/public) that used for uploads owned by www-data user (PHP-FPM user) by default and the default container user (wodby) has no writing permissions. So if you run a command that creates files in a public directory you will get insufficient permissions error. You can fix this problem by giving writing permissions for files directory to the owner's group (user wodby is a member of www-data group) by using one of the helper scripts:

sudo files_chmod /mnt/files/public

When you manually import files under wodby user you should change files ownership to www-data user to let PHP-FPM create new files in directories, run the following command to change the ownership:

sudo files_chmod /mnt/files/public

Helper scripts scope

files_chmod and files_chown are the only sudo commands available to wodby user and can be applied only to directories under /mnt/files .

For mode details about users and permissions in PHP container see

Codebase directory permissions

The codebase owned by the default wodby (uid/gid 1000) user. If you need to give writing permissions to PHP-FPM (www-data user with uid/gid 82) to a directory outside on public files directory you can either access a container as root user or change it from the host server (single-server infrastructure):

chown -R 1000:82 /srv/wodby/instances/[INSTANCE_UUID]/app/path-to-directory
chmod -R 775 /srv/wodby/instances/[INSTANCE_UUID]/app/path-to-directory


You can add NewRelic APM monitoring for PHP by adding environment variables PHP_NEWRELIC_ENABLED=1 and PHP_NEWRELIC_LICENSE with your license number to PHP-FPM container. Application name will be automatically set to [Wodby Application Name] - [Wodby Instance Name], if you want to change it, use PHP_NEWRELIC_APPNAME.


Must know before using profiler

  • Both XHProf and Xdebug profiling decreases performance and increases resources usage, especially xdebug. Try to avoid using in production
  • Traces files take a lot of disk space and may cause out of disk space very quickly


Enable XHProf extension (from Tideways) by adding the environment variable $PHP_XHPROF=1 to your PHP container.

Use the following example snippet to profile your code:

// Start profiling.
if (extension_loaded('tideways_xhprof')) {

// Code which should be profiled.
// ...

// Store profile.
if (extension_loaded('tideways_xhprof')) {
    $xhprof_out = '/mnt/files/private/xhprof';

    if (!file_exists($xhprof_out)) {

    file_put_contents(sprintf('%s/%s.%s.xhprof', $xhprof_out, uniqid(), 'web'), serialize(tideways_xhprof_disable()));

Once traces files generated you can view and analyze your traces via XHProf viewer

Xdebug profiler

Enable XDebug profiling by adding the following environment variables to your PHP container:


Add XDEBUG_PROFILE=1 param to GET or POST request (or set a cookie) you want to profile. Xdebug will generate profile files in /mnt/files/xdebug/profiler. Click Update in Webgrind to access the new information. See to learn more about xdebug profiling.

Once traces files generated you can view and analyze your traces via Webgrind

Xdebug (remote)

Follow these steps to debug your application instance remotely with xdebug:

  1. Enable xdebug for your instance from [Instance] > Stack > Settings
  2. Set up forwarding for xdebug: copy Xdebug SSH tunnel command from [Instance] > Stack > PHP and run on your local machine
  3. Make sure you have your IDE xdebug listener running on port 9000
  4. Start debugging in IDE
  5. Start your browser debug helper plugin (Chrome or Firefox) and open the page you want to debug

Xdebug (local)

Debugging web requests

  1. Uncomment these lines for PHP service in your docker-compose file
    PHP_XDEBUG: 1                 
  2. Restart containers (make)
  3. Start debugging in IDE
  4. Start your browser debug helper plugin (Chrome or Firefox) and open the page you want to debug. Alternatively, enable auto start by adding PHP_XDEBUG_REMOTE_AUTOSTART=1

Debugging CLI requests

  1. Enable Xdebug as described in the previous section
  2. Uncomment the following environment variables for PHP service in your composer file
    PHP_IDE_CONFIG: serverName=my-ide
  3. Configure your IDE
  4. Perform configuration as described below depending on your OS and Docker version:
Linux, Docker
  1. Uncomment PHP_XDEBUG_REMOTE_HOST: for PHP service (if you have docker 18.03+ you can specify host.docker.internal instead of the IP address)
  2. Restart containers (make)
macOS, Docker
  1. Uncomment PHP_XDEBUG_REMOTE_HOST: for PHP service (just a random IP that very likely won't be used by anything else).
  2. Restart containers (make)
  3. You also need to have loopback alias with IP from above. You need this only once and that settings stays active until logout or restart:
    sudo ifconfig lo0 alias
  4. To add the loopback alias after a reboot, add the following contents to /Library/LaunchDaemons/docker4drupal.loopback.plist:
    <plist version="1.0">
        <string>Default Loopback alias</string>
  1. Uncomment PHP_XDEBUG_REMOTE_HOST: for PHP service (default IP of Docker NAT).
  2. Restart containers (make)
  3. Allow listen connection for your IDE in Windows Firewall > Allow an app ..

Also, you might need to add the following lines to your hosts file (see related github issue):         localhost       localhost

IDE configuration

You must additionally configure your IDE to debug CLI requests.

  1. Open Run > Edit Configurations from the main menu, choose Defaults > PHP Web Page in the left sidebar
  2. Click to [...] to the right of Server and add a new server
    • Enter name my-ide (as specified in PHP_IDE_CONFIG)
    • Enter any host, it does not matter
    • Check Use path mappings, select path to your project and enter /var/www/html in the right column (Absolute path on the server)
  3. Choose newly created server in "Server" for PHP Web Page
  4. Save settings


See PostgreSQL stack documentation.


See Redis stack documentation.


Rsyslog can be used to stream your applications logs. It's similar to using syslog, however there's no syslog in PHP container (one process per container). Rsyslog will stream all incoming logs to a container output.

You can use Monolog with SyslogUdpHandler to stream logs to rsyslog


A duplicate of PHP container runs with SSH daemon (instead of FPM). You can find access information on [Instance] > Stack > SSH

Public SSH keys from your Wodby profile will be added automatically for all users that have access to an instance.


See Varnish stack documentation.


Webgrind allows you view and analyze Xdebug profiler output and generate call graphs for visualisation.

XHProf viewer

XHProf viewer allows you view and analyze XHProf traces output and generate call graphs for visualisation.