Publish list of the extensions available through the Bref PHP container

[jamesmacwhite]

For the supported PHP versions available to be defined through the Craft Cloud YAML file, it would be great if there could be a way to see the PHP info page in a sample PHP Bref container that's running on Craft Cloud to see the detailed PHP info. For security reasons the phpinfo() function is being filtered out by the Craft Cloud WAF.

Fortrabbit do this through:

https://phpinfo-81.frb.io/
https://phpinfo-82.frb.io/
https://phpinfo-83.frb.io/
https://phpinfo-84.frb.io/

Similar to #110, I recently used a PHP function included in one of the common extensions that is often bundled in PHP, but it is not available on Craft Cloud. Until I committed the code to at least one Craft Cloud environment. I had no indication of this being a problem.

Ideally my development environment should match Craft Cloud so I can enable and disable extensions accordingly to avoid issues.

Alternatively, if it is possible to publish the core Bref PHP extensions and anything else the PHP container uses as a general list, that would provide additional insight to try and align my development environment to Craft Cloud, to avoid using a function which is not enabled due to the extension being not part of the Bref PHP image.

[jamesmacwhite]

I was able to mostly determine this through the PHP info data in utilities when checking a Craft Cloud environment, but maybe worth having in the docs somewhere of all the core PHP extensions available for future reference.

[timkelty]

@jamesmacwhite great idea – we'll get this documented.

Side note: while not really intended for public consumption, we do have a DDEV plugin we use internally to simulate the Cloud environment as closely as possible: https://github.com/craftcms/ddev-craft-cloud

That is likely a bit more than you want or need, as you probably just want the PHP configuration to match, not the entire stack.

[jamesmacwhite]

Thanks @timkelty! I did notice the DDEV plugin and thought it was interesting! I think it is more the PHP configuration aspect, because the other areas, I don't need to replicate a serverless environment locally. For Craft Cloud development it is good of course, but having things like Imagemagik available for local image transforms and such would be fine under DDEV for just a local environment itself.

This feature of DDEV, allows overwriting .ini files. In this case extensions that are being loaded can be basically disabled by a blank .ini file of the same name e.g. .ddev/php/20-calendar.ini which then prevents the extension from being loaded and therefore cannot be used locally and would throw an undefined function error like Craft Cloud.

The list I ended up with removing to get a more accurate extensions list.

20-apcu.ini
20-assert.ini
20-calendar.ini
20-ldap.ini
20-msgpack.ini
20-sysvmsg.ini
20-sysvsem.ini
20-sysvshm.ini
20-yaml.ini
25-memcached.ini

Memcached has some dependency to msgpack I think, so it had to be removed by dependency, although given DDEV locally doesn't need either and Craft Cloud uses Redis anyway, not really an issue.

As an extra bonus, you can also have a local DDEV craft-cloud.ini which sets the core PHP configuration vars, in particular if you want to play by Craft Cloud infrastructure rules, settings the post_max_size and max_execution time to the Craft Cloud values so you basically force your environment to be like serverless.

The core list of extensions available in the Bref PHP container would be good for general info though, certainly as a general doc. Hopefully #110 can become a feature, so it isn't as a big issue if you can customise the container, but for now, that would be a good starting point.