PHP-FPM

Description

The PHP-FPM component is responsible for managing the PHP-FPM service and all settings around it.

Settings

• Version - The version of PHP you would like to run. (see Versions)
• Post rollup commands - This allows you to run a common set of commands before the instance is ready. This is useful if you require a package such as gulp to build your site that isn't available by default.
• Run command as - The user to run the "Post rollup commands" as.

The root user, is a true root user. This means it is possible to break your instances, please proceed with caution

• Enable Xdebug - If Xdebug should be enabled on your instance.
  This setting has no effect on your production instance, it will just set the default value that is inherited by all development instances.
• Debug Location - If you would like to use remote debug, the location you would like to run the debugger.
• Outgoing Mail - This value has no effect on live instances, it simply sets a default for development instances. If set to disabled, no email will leave the instance at all. If set to enabled email will leave and likely hit spam folders. If set to 'Intercept with Mailcatcher', all outgoing mail will be sent but caught by the MailCatcher helper, and not go any further.
• Additional Config - Any additional PHP setting you would like.

PHP Versions

*Deprecated Versions do not receive any updates.
**Versions no longer supported can be used, but our support team will be unable to assist with issues.

Memory Limits

The `memory_limit` for non dedicated production instances (production instances <= medium size) have a fixed 2G memory limit. Large or X-Large can have any memory limit (upto the amount of memory available on the server).

Composer

If there are multiple versions of composer available composer, MDOQ will ensure the composer version you have selected will always be available with

 composer

If you are installing packages from source, e.g Github you may need to add Githubs keys to the known keys. You will likely see an error like The authenticity of host 'github.com"in the composer install logs. You can do this by adding 

su - magento -c "if [ ! -d ~/.ssh ]; then mkdir ~/.ssh; fi; ssh-keyscan github.com >> ~/.ssh/known_hosts"

to your custom PHP-FPM configuration.

Environment Variables

Within the PHP-FPM container (or via SSH) the following environment variables are available. These environment variables can be useful in configuration as code. For more information on configuration as code please see the Post Roll Up Actions Component.

1111

bug
release_candidate
production_micro
production_small
production_medium
production_large
production_xlarge
production_aws

bug-fix-001

yes
no

2.2.23

Custom Configuration

In some circumstances you may need to configure PHP (i.e install additional packages). Doing this is simple.

1. Create the file `mdoq/php-fpm/configure` (make it executable)
   

   #!/bin/bash -xe
   # apt install -y nano    

2. Add this file to source control
3. Instance Settings > PHP-FPM > Post Rollup commands: 
   

   cd /home/magento/htdocs; ./mdoq/php-fpm/configure

4. Instance Settings > PHP-FPM > Run commands as: `root`
   N.B if you run as root do NOT run magento commands.
5. Save settings
6. Sync PHP-FPM

Related Articles

• Working with XDEBUG