eZ Publish makes use of and depends on five important things:
See the The web servers page
PHP is free software and can be downloaded from http://www= .php.net. The full list of extensions needed can be found on the requirements page. Info on some caveats= can be found below.
Make sure that zlib support in PHP is enabled, ot= herwise the setup wizard will= not be able to unpack downloaded packages during the installation process.=
In most cases, DOM functions are enabled by defaul= t as they are included in the PHP core. However, some Linux distributions h= ave PHP without compiled-in support for DOM. Instead, they provide DOM as a= shared module in a separate RPM package called "php-xml".
Since version 5.0, it i= s necessary to have PHP CLI ins= talled, as using php from the command line is needed during the se= tup process. Also, some features like notifications, delayed search indexing, upgrade scripts, = the collaboration system (content approval), clearing caches from within th= e command line, etc. will not work without php cli access.
It is recommended to enable CURL= support, otherwise some features like outbound connection= s via proxy and SSL support for eZSoap will not work.
eZ Publish 5.3-alpha1/2004.01 and higher needs "memory_limit =3D 2=
56M" in order to complete the setup wizard, or to execute its tests.=
Earlier releases needed "memory_limit=3D 128MB" as is the=
default in PHP.
memory_limit =3D 256M #prior to eZ Publish 5.3-alpha1/2004.01 #memory_limit =3D 128M=20
You need to set the "date.time=
zone" value in the "php.ini" configuration file. If this s=
etting is not specified, you will most likely receive error messages like <=
em>"It is not safe to rely on the system's timezone settings" when run=
ning eZ Publish on PHP 5.
The following example shows how the correspon=
ding line in "php.ini" looks like:
date.timezone =3D <timezone>=20
Don't forget to restart Apache after editing "php.ini".
eZ Publish sessions are handled by the Symfony stack, t=
hrough session handlers. For that to be set up, additional=
YAML configuration are required, which you can find in the&nb=
sp;Session chapter.
See the Symfony documentation for t=
he recommended php.ini settings for Symfony, as well as the Vhost example for the recommended
eZ Publish stores data structures and content using a relational= database. This means that a database server has to be available f= or eZ Publish at all times. Follow this link to the eZ Publish requirements pa= ge to find which database solutions eZ Publish is compatible with.
eZ Publish 5 requires a UTF-8 database and support for =
transactions, which for MySQL means using the InnoDB storage engine.
The Setup Wizard will auto= matically detect the database server during operation of the setup wizard i= f it is running on the same computer that operates as web server.
InnoDB storag=
e engine.
Even if you are not going to run eZ Publish in a clustered environment, =
the use of InnoDB is required. This storage engine makes it po=
ssible to use transaction-safe tables in a MySQL database.
Contact your database administrator if you are unsure about whether
MySQL can be tweaked with a lot of settings, but one setting which is re= quired to set to a higher value is innodb_buffer_pool_size , by default it is set to 8MB, but it needs at least to be set to 128MB, = or as the MySQL doc says up to 80% of system memory on dedicated database s= erver.
Known issue with running PHP5.3 on MySQL: Some peo=
ple (like Windows users with both IPv4 and IPv6 installed ) experience prob=
lems connecting to the database server using host names like "localho=
st". If you experience problems, try using IPv4 address like "=
127.0.0.1". This is due to a connectivity problem when running PHP5.=
3 on MySQL. So, please replace the database server name "localhost" with the IP address of the machine, or "127.0.0.1", whic=
h is reserved for the local host.
If you want to use PostgreSQL, make sure the "pgcrypto" module is installed. On Linux/UNIX, you =
may need to install a separate package called "postgresql-contrib" which contains the "pgcrypto" module. The "pgcrypto=
" module provides cryptographic functions for PostgreSQL, including =
the "digest" function, which is needed for eZ Publish.
When setting up a PostgreSQL database for eZ Publish, you will have
To be able to use eZ Publish on oracle you will need the eZ Publish Ext= ension for Oracle=C2=AE Database extension, as well as the php oci8 extension.
Supported only on eZ Publish 5.0, which is also the last version support= ing Oracle on full legacy installations, which support does not include RES= T API usage or new "Symfony / eZ Platform" stack. Support is planned to ret= urn with one of the first releases of "eZ Platform", aka "6.x".
In order to resize, convert or modify images, eZ Publish needs to make u= se of an image conversion system. One of the following sof= tware packages (both are free) can be used:
ImageMagick supports more formats than GD and usually produces better re= sults (better scaling, etc.). The setup wizard will automatically detect th= e pre-installed image conversion system(s).
The installation and setup of required software solutions (outlined abov= e) is far beyond the scope of this document. Please refer to the homepage a= nd documentation of the different software solutions.
Composer will need GD to run.
eZ Publish stores all binary content (e.g. images, PDFs, etc.) in =
var/storage using a similar folder structure to the content tree, cr=
eating one folder for each object.
In most file systems used under Linu=
x (especially ext2 + ext3) there is a hard limit of 32.000 sub-folders to t=
he maximum which can be created in one folder. This means that it i=
s not possible to store more than 31999 objects under one parent object.
To get around this limitation without changing the file system, you can = split your content tree so that you don't have more than 3= 2k content files (example: images) in the same folder.
Other file systems support more file/folder entries per folder:
Please be aware that it's not advisable to run eZ Publish on NFS file sy= stems as you may experience issues. The cause of the issues may be = performance, as NFS will slow down on heavy network traffic, slow = access to files, or file access concurrency regarding file lock. Also, eZ P= ublish currently uses the flock() = PHP function, which is not considered stable for NFS shares.
During execution of the setup = wizard, the web server will need to download some content from the inte= rnet.