eZ Publish makes use of and depends on five important things:
The first three things should be in place before an eZ Publish installat= ion is deployed. The image conversion system is optional and is only needed= if you're planning to use eZ Publish with images. The web server and the s= erver-side PHP scripting engine have to run on the same machine. The databa= se server may run on a different computer.
Please visit the requirements pa= ge to check if your platform fully supports installing eZ Publish, then= come back for the extra details which follow.
Currently, only the Apache web server is supported. On Linux/UNIX= based systems, it is recommended to use the latest version of the 2.2.x br= anch (applies also to cluster mode). Note that it must run in "prefork" mod= e instead of "threaded" mode - the reason for this is because some of the l= ibraries that PHP extensions use might not be thread-safe.
Nginx and Lighttpd are known to work as well but are currently not suppo= rted. "Rewrite" rules for those web servers can be found online, f.e. on th= e forums on share.ez.no.
On Windows, it is recommended to use MS IIS 7 or higher (with Microsoft = URL Rewrite Module 1.1 or higher). Apache 2.x for Windows is not supported = since it only exists in "threaded" mode.
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 b= elow:
Make sure that zlib support in PHP is enabled, otherwise the setup wizard will not be able to unpac= k downloaded packages during the installation process.
In most cases, DOM functions are enabled by default as they are inc= luded in the PHP core. However, some Linux distributions have PHP without c= ompiled-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 installed, = as using php from the command line is needed during the setup process. Also= , some features like noti= fications, delayed search indexing, upgrade scripts, the collaboration = system (content approval), clearing caches from within the command line, et= c. will not work without php cli access.
It is recommended to enable CURL support, otherwise some features = like outbound connections via proxy and SSL support for eZSoap= will not work.
eZ Publish needs at least 64 MB of memory in order to complete the setup= wizard. Normal operation requires about 32 MB. However, it is highly recom= mended that you keep the 64 MB setting since eZ Publish consumes a lot more= memory as you reindex the content, execute upgrade scripts, etc. Multiling= ual sites will also require at least 64 MB.
As of PHP 5.2.1 and later, there is no need to change the default "
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 "=
It is not safe to rely on the system's timezone settings" when running eZ P=
ublish on PHP 5. The following example shows how the corresponding line in =
"php.ini" looks like:
date.timezone =3D <timezone>=20
Refer to the PHP documentation for the list of supported time=
zones. Don't forget to restart Apache after editing "php.ini".=
eZ Publish sessions are handled by the Symfony stack, through session ha=
ndlers. For that to be set up, additional yml config=
uration are required, which you can find in the Session chapter.
See the Symfony documentation f=
or the recommended php.ini settings for Symfony, as well as th=
e Vhost example for the recommended=
php.ini settings for eZ Publish.
Zeta Components (formerly eZ Components) is an enterprise-ready, general= purpose library of PHP components which can be used used independently or = together for PHP application development. They can be downloaded from http://ezcomponents.org/download, or installed using different me= thods such as Pear, Composer, Github etc... The online docum= entation has detailed instructions on installing them on the webserver.=
The correct version of the Zeta Components required for running eZ Publi= sh always comes bundled with eZ Publish package itself, so there is no need= to install them separately.
It is possible to use a single instance of the Zeta Components library a= nd share it between multiple installations of eZ Publish. Such configuratio= n is complex and falls outside the scope of this document.
eZ Publish stores miscellaneous data structures and actual content using= a relational database. This means that a database server has to be availab= le for eZ Publish at all times. Follow this link to the eZ Publish requirements page to find which database solutio= ns eZ Publish is compatible with.
eZ Publish 5 requires a UTF-8 database and support for transactions, whi=
ch for MySQL means using the InnoDB storage engine.
The setup wizard will automatically detect the database server during op= eration of the setup wizard if it is running on the same computer that oper= ates as web server.
Note that eZ Publish 5 does not support clustering mode for PostgreSQL databases. The clustering=
code is optimized for best performance on MySQL databases using the =
InnoDB storage engi=
ne.
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. (Database transa=
ction support is enabled by default in eZ Publish. This feature makes the s=
ystem less vulnerable to database errors and inconsistencies due to aborted=
requests.) Contact your database administrator if you are unsure about whe=
ther InnoDB is available on your server.
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 defaul= t it is set to 8mb, but it needs at least to be set to 128mb, or as the mys= ql doc says up to 80% of system memory on dedicated database server.
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 "localhost<=
/code>" with the IP address of the machine, or "127.0.0.1", wh=
ich is reserved for the local host.
If you want to use PostgreSQL, make sure the " In order to resize, convert or modify images, eZ Publish needs to make u=
se of an image conversion system. One of the following software packages (b=
oth 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. eZ Publish stores all binary content (e.g. images, PDFs etc) on disc in =
To get around this limitation without changing the file system, you can =
split your content tree so that you don't have more than 32k content files =
(example: images) in the same folder. Other file systems support more file/folder entries per folder: Note that those filesystems might not be fully supported by eZ Publish, =
please check out the requirements p=
age for details. 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 performa=
nce, as NFS will slow down on heavy network traffic, slow access to files, =
or file access concurrency regarding file lock. Also, eZ Publish currently =
uses the flock()<=
/a> PHP function, which is not considered stable for NFS shares. NFS should only be used to store distributed data such as cache, or bina=
ry files, in clustered environments. During execution of the setup wizard, the web server will need to downlo=
ad some content from the internet. If the web server can not access directly the internet, or if it has to =
go through a proxy, workarounds have to be taken. See the setup wizard documentation page for possible=
workaroundspgcrypto" module is installed. On Linux/UNIX, you =
may need to install a separate package called "postgresql-contrib" (refer to the PostgreSQL documentatio=
n for more information), which contains the "pgcrypto" mod=
ule. The "pgcrypto" module provides cryptographic functions fo=
r PostgreSQL, including the "digest" function, which is needed for eZ Publi=
sh. When setting up a PostgreSQL database for eZ Publish, you will have to =
register these functions in the database. Refer to the "Setting up a databa=
se" part of the " Installing eZ Publish on a Linux/UNIX based system" and "=
Installing eZ Publish on Windows=
" documentation pages (depending on the target OS) for more information.
Image conversion system (optional)
Limitation on some file systems whe=
n storing large number of content files
var/storage using a similar folder structure to the content tr=
ee, creating one folder for each object. In most file systems used under Li=
nux (especially ext2 + ext3) there is a hard limit of 32.000 to the maximum=
number of sub-folders which can be created in one folder. This means that =
it is not possible to store more than 31999 objects under one parent object=
.
eZ Publish on NFS file systems
Netw=
ork connectivity