Check custom PHP settings

After pushing the php.ini changes to your Cloud environment, you can check that the custom PHP configuration has been added to your environment. For example, use SSH to log in to the remote environment and view the file using something similar to the following:

cat /etc/php/<php-version>/fpm/php.ini
WARNING
If you use Cloud Docker for Commerce for local development, see Docker service containers for information about using a custom php.ini file in a Docker environment.

Enable extensions

You can enable or disable PHP extensions in the runtime:extension section. Also, the extensions specified become available in the Docker PHP containers.

IMPORTANT
Before enabling extensions, it is important to understand that the PHP version must be compatible with the operating system hosting the project. Your project environment might require an OS upgrade by the Infrastructure team before you can proceed.

Example in .magento.app.yaml file:

runtime:
    extensions:
        - sockets
        - sodium
        - ssh2
    disabled_extensions:
        - bcmath
        - bz2
        - calendar
        - exif

Use SSH to log in to an environment and list the PHP extensions.

php -m

For details about a specific PHP extension, see the PHP Extension List.

The following table shows the supported PHP extensions when deploying Adobe Commerce on the Cloud platform.

Default extensionsInstalled extensions that cannot be uninstalledExtensions that can be installed and uninstalled as needed
bcmath
bz2
calendar
exif
gd
gettext
intl
libxml
mysqli
opcache
pcntl
pdo_mysql
Reflection
soap
sockets
SPL
standard
swoole
sysvmsg
sysvsem
sysvshm
zip
zlib
ctype
curl
date
dba
dom
fileinfo
filter
ftp
hash
iconv
json
mbstring
mysqlnd
openssl
pcre
pdo
pdo_sqlite
phar
posix
readline
session
sqlite3
tokenizer
xml
xmlreader
xmlwriter
geoip
gmp
igbinary
imagick
imap
ldap
mailparse
mcrypt
msgpack
mysqli
oauth
pdo_mysql
propro
pspell
raphf
recode
redis
shmop sockets
sodium
ssh2
tidy
xdebug
xmlrpc
xsl
yaml

PHP module requirements are tied to the Adobe Commerce version. See PHP requirements.

Extension support

For Pro projects, the following extensions require additional support to install:

  • ioncube
  • sourceguardian

For example, to set up PHP to execute only SourceGuardian-protected scripts in all environments, the following option must be set in the php.ini file:

[SourceGuardian]
sourceguardian.restrict_unencoded = "1"

See section 3.5 of the SourceGuardian documentation. This is a link to a PDF.

Submit an Adobe Commerce Support ticket for help with installing these PHP extensions in all Production environments and Pro Staging environments. Include your updated .magento/services.yaml file, .magento.app.yaml file with the updated PHP version and any additional PHP extensions. For changes to a live Production environment, you must provide a minimum of 48 hours notice. It can take up to 48 hours for the Cloud infrastructure team to update your project.

WARNING
PHP compiled with debug is not supported and the Probe may conflict with XDebug or XHProf. Disable those extensions when enabling the Probe. The Probe conflicts with some PHP extensions like Pinba or IonCube.
Previous pageConfigure application deployment
Next pageApplication properties

Commerce