Skip to content

Requirements and System Configuration

eZ Platform Cloud / Platform.sh

If you're using a PaaS provider such as the native eZ Platform Cloud, or its underlying Platform.sh offering, you can get started using the bundled config which contains recommended initial setup, and thus skip this step.

NOTE: Usage on eZ Platform Cloud/Platform.sh is limited to the featureset of platform.sh, however you can also use additional services like for instance S3, GridFS, etc., as long as you host that service yourself and set up the necessary credentials to use it, as you would normally do when hosting the application on-premise.

Server

eZ software is built to rely on existing technologies and standards. The minimal setup is PHP,  MySQL/MariaDB, and Apache/Nginx. Recommendation for production setups is to use Varnish/Fastly, Redis, NFS/EFS/S3 and Solr in a clustered setup.

For supported versions of these technologies see Recommended and Supported setups below.

These setups are tested by QA and are generally recommended setups. For security and performance we furthermore recommend use of the newer versions of components below.

Debian Ubuntu RHEL / CentOS
Operating system 9.x "Stretch" 18.04 LTS "Bionic" 7.x
Web Server Nginx 1.10
Apache 2.4
Nginx 1.14
Apache 2.4
Nginx 1.10 (latest via RHSCL)
Apache 2.4
DBMS MariaDB 10.1
MySQL 5.5
MariaDB 10.1
MySQL 5.7*
MariaDB 10.1 (latest via RHSCL)
MariaDB 10.0 (latest via RHSCL)
MySQL 5.6 (latest via RHSCL)
MariaDB 5.5
PHP PHP 7.1 (Either using packages in testing, or deb.sury.org) PHP 7.2 PHP 7.1 (latest via RHSCL)
PHP packages php-cli
php-fpm
php-mysql or php-pgsql
php-xml
php-intl
php-curl
php-gd or php-imagick
php-cli
php-fpm
php-mysql or php-pgsql
php-xml
php-mbstring
php-intl
php-curl
php-gd or php-imagick
php-cli
php-fpm
php-mysqlnd or php-pgsql
php-xml
php-mbstring
php-process
php-intl
php-pear (optional, provides pecl)
php-gd or php-imagick (via pecl)
Cluster PHP packages
php-redis (via pecl) php-redis (via pecl) php-redis (via pecl)
Search Solr (recommended; for performance, features and search quality):

Solr 6 or higher Currently tested with Solr 6.6.2

Oracle Java/Open JDK: 8
Graphic Handler GraphicsMagick or ImageMagick or GD
Clustering Linux NFS or S3/EFS (for IO, aka binary files stored in content repository)
Redis 3.0 or higher (preferably a separate volatile-ttl instance for sessions, and an allkeys-lru/allkeys-lfu instance for cache)
Varnish 4.1 or higher with varnish-modules or Fastly using our bundle provided with eZ Platform Enterprise (for HttpCache)
Filesystem Linux ext3 / ext4
Package manager Composer

Supported setups

Supported setups are those we perform automated testing on. For security and performance we generally recommend (unless otherwise noted and marked with *) using the newer versions of components below.

  • OS: Linux
  • Web Servers:
    • Apache 2.4, with required modules mod_rewrite, mod_env and recommended: mod_setenvif, mod_expires
      • event MPM is recommended, if you need to use prefork you'll also need the mod_php module
    • Nginx 1.10, 1.12, 1.14
  • DBMS
    • MySQL 5.5.3 and higher, 5.6*, 5.7*
    • MariaDB 5.5, 10.0, 10.1, 10.2*
  • PHP

    • 7.1
    • 7.2
  • Cluster

  • PHP extensions/modules

    • curl
    • ctype
    • fileinfo
    • iconv
    • intl
    • mbstring
    • opcache
    • pdo
      • pdo mysql (with mysqlnd)
    • posix
    • reflection
    • xml
    • xsl
    • zip
    • php-redis or php-memcached (3.x)

* Note: Mysql 5.7 and MariaDB 10.2 changes how certain queries are parsed and is known to have issues with content attribute sorting queries in legacy because of that at the moment, MySQL 5.6 technically works but executes several hundred times slower on said queries. Because of this we overall recommend MariaDB 10.1 and 10.0, and don't offically support MySQL 5.6/5.7 and MariaDB 10.2 in use with legacy at the moment.

Development and Experimental setups

eZ Platform, the foundation of all eZ software, can theoretically run and execute on many more setups than the ones listed as recommended and supported, including any operating system supported by PHP, on a PHP 7.1 version or higher that pass the Symfony requirements, using cache solutions technically supported by Symfony Cache component, using databases supported by Doctrine DBAL, and using a binary file storage solution supported by FlySystem.

Examples of Development setups:

  • OS: Windows, Mac OS X, Linux
  • Filesystem: NTFS, HFS+/APFS, ...

Examples of Experimental setups:

  • OS: Any system supported by PHP
  • Filesystem: BTRFS, AUFS, ...
  • IO: Azure, (S)FTP, GridFS, ...
  • Databases: Postgres, MSSQL, Oracle (As in technically supported by Doctrine DBAL which we use, but none supported by our installer at the moment, and Oracle and MSSQL is not covered by automated testing)

While all these options are not actively supported by eZ Systems, they are community supported. Meaning you can use them with both open source edition and enterprise edition, however if you encounter issues best way to handle them is via contribution, and any such efforts made to improve support for these technologies can contribute to the technology being supported by eZ Systems in the near future.

Client

eZ software is developed to work with any web browser that support modern standards, on any screen resolution suitable for web, running on any device. However for the Editorial and Administration User Interfaces you'll need; a minimum of 1024-by-768 screen resolution, a desktop or tablet device, and a recommended/supported browsers found below.

These setups have been undergone some additional manual testing and is known to work.

  • Mozilla® Firefox® most recent stable version
  • Google Chrome™ most recent stable version
  • Microsoft® Edge® most recent stable version

Supported browsers

  • Apple® Safari® most recent stable version, desktop and tablet
  • Opera® most recent stable version, or higher, desktop and mobile 

Please note that the user interface might not look or behave exactly the same across all browsers as it will gracefully degrade if browser does not support certain features.

Read the Docs