Install eZ Platform¶
Installation for production is only supported on Linux.
To install eZ Platform for development on macOS or Windows, see Install on macOS or Windows.
Prepare work environment¶
To install eZ Platform you need a stack with your operating system, MySQL and PHP.
You can install it by following your favorite tutorial, for example: Install LAMP stack on Ubuntu.
You also need
git for version control.
Before getting started, make sure you review the requirements page to see the systems we support and use for testing.
Install Composer, the PHP command line dependency manager. Use the package manager for your Linux distribution. For example on Ubuntu:
Install Composer locally
If you want to install Composer inside your project root directory only, run the following command in the terminal:
After this you need to replace
php -d memory_limit=-1 composer.phar in all commands below.
Get eZ Platform¶
There are two ways to get eZ Platform. The result is the same, so you can use the way you prefer:
Authentication tokens for eZ Enterprise
If you are installing eZ Enterprise, from this point refer to Install eZ Enterprise.
A. Download eZ Platform¶
You can download eZ Platform from two sources:
1. Download an archive
- For open-source eZ Platform, download from ezplatform.com.
- For licensed eZ Enterprise, download from the Support portal.
Extract the archive into the location where you want your project root directory to be.
2. Clone GitHub repository
You can also clone the GitHub repository.
Check out a tag (e.g.
git checkout v1.13.4) for use in a project.
Use branches (e.g.
1.13) only when contributing.
Install dependencies with Composer¶
Composer will look inside the
composer.json file and install all of the packages required to run eZ Platform.
From the folder into which you downloaded eZ Platform, run:
B. Create project with Composer¶
You can also use Composer to instantly create a project in the current folder with all the dependencies:
You can set different version constraints:
specific tag (
v1.7.8), version range (
~1.13.0), stability (
For example if you want to get the latest stable 1.13 LTS release, with a minimum of v1.13.3, use:
Provide installation parameters¶
After a moment the installer will ask you to provide a few parameters:
- Choose a secret; it should be a random string, made up of at least 32 characters, numbers, and symbols. This is used by Symfony when generating CSRF tokens, encrypting cookies, and for creating signed URIs when using ESI (Edge Side Includes).
- You can accept the default options for
- Select a
database_nameor accept the default one.
- Provide your
The app secret is crucial to the security of your installation. Be careful about how you generate it, and how you store it. Here's one way to generate a 64 characters long, secure random string as your secret, from command line:
Do not commit the secret to version control systems, or share it with anyone who does not strictly need it. If you have any suspicion that the secret may have been exposed, replace it with a new one. The same goes for other secrets, like database password, Varnish invalidate token, JWT passphrase, etc.
After changing the app secret, make sure that you clear the application cache and log out all the users. For more information, see Symfony documentation.
If you want to change any of these parameters later, you can do it in
Create a database. Run the following command inside MySQL Shell:
Install eZ Platform¶
Install eZ Platform with:
For eZ Enterprise, use:
Before executing it make sure that the database user has sufficient permissions.
If Composer asks for your token, you must log in to your GitHub account and generate a new token (edit your profile, go to Developer settings > Personal access tokens and Generate new token with default settings). This operation is performed only once when you install eZ Platform Enterprise Edition for the first time.
Use PHP's built-in server¶
At this point you can use PHP's built-in server:
php app/console server:start.
PHP's built-in server is for development use only. For security and performance reasons it should not be used in production.
Prepare installation for production¶
Set up permissions¶
For development needs, the web user can be made the owner of all your files (for example with the
www-data web user):
web/var need to be writable by CLI and web server user.
Future files and directories created by these two users will need to inherit those permissions.
For security reasons, in production web server should not have write access to other directories than
var. Skip the step above and follow the link below for production needs instead.
You must also make sure that the web server cannot interpret files in the
var directory through PHP. To do so, follow the instructions on setting up a virtual host below.
To set up permissions for production, it is recommended to use an ACL (Access Control List). See Setting up or Fixing File Permissions in Symfony documentation for information on how to do it on different systems.
Set up virtual host¶
Option A: Scripted configuration¶
Use the included shell script:
/<your installation directory>/bin/vhost.sh to generate a ready to use
Check out the source of
vhost.sh to see the options provided.
Option B: Manual configuration¶
/<your installation directory>/doc/apache2/vhost.template to
/etc/apache2/sites-available as a
Modify it to fit your project.
/<your installation directory>/web as the
Uncomment the line that starts with
#if [SYMFONY_ENV] and set the value to
depending on the environment you want:
Enable virtual host¶
When the virtual host file is ready, enable the virtual host and disable the default:
Finally, restart the Apache server. The command may vary depending on your Linux distribution. For example of Ubuntu use:
Open your project in the browser and you should see the welcome page.
If you are installing eZ Enterprise, take a look at Installing eZ Enterprise for additional steps.
eZ Launchpad for quick deployment
If you want to get your eZ Platform installation up and running quickly, you can use Docker-based eZ Launchpad, supported by the eZ Community, which takes care of the whole setup for you.
See the Security checklist for a list of security-related issues you should take care of before going live with a project.