Path / documentation / ez publish / technical manual / 3.7 / installation / normal installation / requirements for doing a no...

Caution: This documentation is for eZ Publish legacy, from version 3.x to 5.x.
For 5.x documentation covering Platform see eZ Documentation Center, for difference between legacy and Platform see 5.x Architecture overview.

Requirements for doing a normal installation

eZ publish makes use of and depends on four important things:

  1. A web server
  2. A server-side PHP scripting engine
  3. A database server
  4. An image conversion system (optional)

The first three things should be in place before an eZ publish installation 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 server-side PHP scripting engine has to run on the same machine. The database server may run on a different computer. For the moment, the following software solutions can be used:

Web server

Currently, only the Apache web server is supported. It is recommended to use the latest version of the 1.3 branch. However, it is possible to use the 2.x series. When using Apache 2.x, it must run in "prefork" mode instead of "threaded" mode - the reason for this is because the PHP libraries are not threadsafe. Please note that Apache 2.x for Windows only exists in "threaded" mode and thus it should not be used to run an eZ publish solution on Windows. The Apache web server is the most popular web server on the planet. It is free, open source and can be downloaded from

Server-side PHP scripting engine

Since most of the eZ publish system is written using the PHP scripting language, a PHP (hypertext preprocessor) server-side engine is needed. Make sure you have PHP 4.4. It is recommended to use the latest version of the 4.4 branch. Please note that eZ publish will not work correctly with PHP 5 and thus PHP 5 should not be used. PHP needs to have compiled-in support for either MySQL or PostgreSQL.

PHP is free software and can be downloaded from


It is strongly recommended to have PHP CLI installed, otherwise some features will not be available.

PHP memory limit issue

eZ publish needs at least 64 MB in order to complete the setup wizard. This means that you'll have to increase the default "memory_limit" setting which is located in the "php.ini" configuration file. (Don't forget to restart apache after editing "php.ini".) Normal operation requires about 16 MB. However, it is highly recommended that you keep the 64 MB setting since eZ publish consumes a lot more memory as soon as you use PDF export feature, reindex the search, etc. Multi-lingual sites that store the content in Unicode (UTF-8) will also require at least 64 MB.

Database server

eZ publish stores miscellaneous data structures and actual content using a database. This means that a database server has to be available for eZ publish at all times. By default, eZ publish is compatible with the following database solutions:

The setup wizard will automatically detect the database server as long as it is running on the same computer that functions as the web server.

If you are going to use PostgreSQL, make sure the "pgcrypto" module is installed. On Linux/UNIX, you may need to install a separate package called "postgresql-contrib" (refer to the PostgreSQL documentation for more information), 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 register these functions in the database as described in the "Setting up a database" part of the installation instructions.

Oracle compatibility

The eZ Publish Extension for Oracle® Database makes it possible to use Oracle as a database for eZ Publish. Please refer to the documentation of the database extension for technical details.

Image conversion system (optional)

In order to scale, convert or modify images, eZ publish needs to make use of an image conversion system. One of the following software packages (both are free) can be used:

ImageMagick supports more formats than GD and usually produces better results (better scaling, etc.). The setup wizard will automatically detect the pre-installed image conversion system(s).

The installation and setup of required software solutions (outlined above) is far beyond the scope of this document. Please refer to the homepage and documentation of the different software solutions.

Balazs Halasy (12/01/2005 1:08 pm)

Svitlana Shatokhina (03/11/2008 1:08 pm)

Svitlana Shatokhina, Julia Shymova


  • Additional requirement for doing a remote install

    Installing on a remote system seems to be possible, though I haven't been able to test it yet. If I'm correct, the following requirements should be added to this section:

    - Console access to the database server (local, rlogin, telnet, etc.)
    - File transfer (write) access to the published directories on the web server (local, ftp, http, etc.).
  • ImageMagik vs GD

    The manual makes it sound like ImageMagik is better (and it may be), but if you don't have GD, the installation Wizard (at least in 3.6.4) says your system is not optimal, and "finetune" recommends you have GD so you can use the text to image feature.
  • question in setup

    can i setup ezpublish with mysql 5??
    • Re: question in setup

      yes, it should work...