The cornerstone of the Autoize™ Marketing Automation Solution is the Mautic container image that is ready to run on any Docker host to deploy new instances of Mautic in minutes. As the foundation of the instances, the robustness of the image is key to ensuring stable and fully-functional deployments of Mautic on the infrastructure.
The image is built using the official PHP Docker image as a starting point, with PHP modules required by Mautic included into the image at build time. Many Docker images use older versions of PHP than are recommended for the current release of Mautic, including versions that might no longer receive security updates.
Newer versions of PHP also bring performance improvements, reducing average server response times. Mautic benefits tremendously from the optimizations in newer versions of PHP, particularly for instances with a large number of contacts and automation sequences. Certain PHP performance benchmarks such as this study by Cloudways suggest that PHP 8.0 is 190% faster than PHP 5.6.
The default upload max filesize (2M) and memory limit (256M) that PHP ships with is also smaller than recommended for Mautic. In the image bundled with our Mautic infrastructure, the PHP config values are modified to support large file uploads and the recommended memory limit for using Mautic in production. This helps prevent timeout errors in the interface, and allows the upload of large media files and downloadable assets.
Mautic also recommends that the default timezone for the server is set in the PHP configuration, so all of our images default to UTC. This ensures that when a timezone is set within the Mautic frontend that it can correctly calculate the offset from UTC to ensure timely campaign deployment.
Out of the box, the container image provided by the Autoize™ Marketing Automation Infrastructure meets the requirements for completing the setup wizard for a new instance of Mautic with no warnings or errors. This saves agency administrators a great deal of time and technical knowledge required in configuring each server manually, like would be required in a virtual machine-based environment.