Installation

=20

General installation guide for all eZ distributions

This installation guide can be followed with any eZ Symfony dis= tribution, here are a list of available distributions from eZ:=

Type	Archive	License	GIT / Composer
eZ Platform - "clean"	share.ez.no/downloads/downloads=	GPL	ezsystems/ezplat= form (INSTALL.md)
eZ Platform - "demo"	Available via Git / Composer	GPL	ezsystems/e= zplatform-demo
eZ Studio - "clean"	support.ez.no/Downloads	BUL (requires eZ Enterprise subscription)=	ezsystems/ezstudio= (INSTALL.md)
eZ Studio - "demo"	support.ez.no/Downloads	BUL (requires eZ Enterprise subscription)=	ezsystems/ezs= tudio-demo

=20

Terms used in this guide

=20

/<root-dir>/: The filesystem path where eZ distribut= ion is installed in. Examples: /home/myuser/www/ or /var/sites/<project-name>/
cli: command line interface. For Linux/BSD/OS X specific comma= nds, use of bash or similar is assumed.

=20

Prerequisites

=20

These instructions assume you have technical knowledge and have already = installed PHP, web server & a database server needed for this = software. For further information on requirements see Requirements page.

Before you start:

- Create Database: installation will ask you for credentials/details for= the database to use.

Right now the installer only supports MySQL and MariaDB, Postgres support w= ill be (re)added in upcoming releases.

- Set php.ini memory_limit=3D256M before running the commands below.

- Optional: You can also set up Solr to be used by eZ dist= ribution and take note of the url it is accessible on.

=20

Installation

=20

1. Install/Extract eZ distribution:

Described below are two methods of installing eZ distribution. What is c= ommon between them is that you should make sure relevant settings are gener= ated into app/config/parameters.yml as a result of this step.<= /p>

parameters.yml contains settings for your database, mail sy= stem, and optionally Solr if search_engine is con= figured as solr, as opposed to default legacy (a limited database-powered search engine).

A. Extract archive (tar/zip) from the relevant address = listed in the table above.<= /p>

Extract the eZ distribution archive to a directory, then execute post-in= stall scripts:

The post-install scripts will ask you to fill in some settings, including d= atabase settings.

=20

$ cd /<directory>/
$ curl -sS https://getcomposer.org/installer | php
$ php -d memory_limit=3D-1 composer.phar run-script post-install-cmd

= =20

B. Install via Composer.

Run composer require with one of the packages listed at the top of this page:

=20

# install ezplatform
composer create-project --prefer-dist --no-dev --keep-vcs ezsystems/ezplatf=
orm

# install ezplatform with demo
composer create-project --prefer-dist --no-dev --keep-vcs ezsystems/ezplatf=
orm-demo
 
# install ezstudio (requires eZ Enterprise license/credentials)
composer create-project --prefer-dist --no-dev --keep-vcs --repository-url=
=3Dhttps://updates.ez.no/bul ezsystems/ezstudio

=20

At the end of the installation process, you will be asked for basic conf= iguration options, such as database credentials.

2. Only for *NIX users S= etup folder rights:

Like most things, Symfony documentation applies here, mean= ing app/cache and app/logs need to be writable by= cli and web server user. Furthermore, future files and directories created= by these two users will need to inherit those access rights. For secur= ity reasons, there is no need for web server to have access to write to oth= er directories.

Change www-data to your web server user:

A. Using ACL on a Linux/BSD system that supports chmod +a

=20

$ rm -rf app/cache/* app/logs/*
$ sudo chmod +a "www-data allow delete,write,append,file_inherit,directory_=
inherit" \
  app/cache app/logs web
$ sudo chmod +a "`whoami` allow delete,write,append,file_inherit,directory_=
inherit" \
  app/cache app/logs web

=20

B. Using ACL on a Linux/BSD system that does not support chmod +a

Some systems don't support chmod +a, but do support another utility call= ed setfacl. You may need to enable ACL support on your partition and instal= l setfacl before using it (as is the case with Ubuntu), in this way:

=20

$ sudo setfacl -R -m u:www-data:rwx -m u:`whoami`:rwx \
  app/cache app/logs web
$ sudo setfacl -dR -m u:www-data:rwx -m u:`whoami`:rwx \
  app/cache app/logs web

=20

C. Using chown on Linux/BSD/OS X systems that don't support ACL

Some systems don't support ACL at all. You will need to set your web ser= ver's user as the owner of the required directories:

=20

$ sudo chown -R www-data:www-data app/cache app/logs web
$ sudo find {app/{cache,logs},web} -type d | xargs sudo chmod -R 775
$ sudo find {app/{cache,logs},web} -type f | xargs sudo chmod -R 664

= =20

D. Using chmod on a Linux/BSD/OS X system = where you can't change owner

If you can't use ACL and aren't allowed to change owner, you can use chm= od, making the files writable by everybody. Note that this method really is= n't recommended as it allows any user to do anything:

=20

$ sudo find {app/{cache,logs},web} -type d | xargs sudo chmod -R 7=
77
$ sudo find {app/{cache,logs},web} -type f | xargs sudo chmod -R 666

= =20

When using chmod, note that newly created files (such as cache) owned by= the web server's user may have different/restrictive permissions. In this = case, it may be required to change the umask so that the cache and log dire= ctories will be group-writable or world-writable (umask(0002) = or umask(0000) respectively).

It may also possible to add the group ownership inheritance flag so new = files inherit the current group, and use 775/664 = in the command lines above instead of world-writable:

=20

$ sudo chmod g+s {app/{cache,logs},web}

=20

E. Setup folder rights on Windows

For your choice of web server you'll need to make sure web server user h= as read access to <root-dir>, and write access to the fo= llowing directories:

app/cache
app/logs

3. Configure a VirtualHost:

A virtual host setup is the recommended, most secure setup of eZ distrib= ution. General virtual host setup template for Apache and Nginx can be foun= d in the doc/ folder of your eZ installation. For the latest v= ersion you can also find it in same doc/ folder in the relevan= t Git repository listed in the = table above.

4. Run installation command:

You may now complete the eZ distribution installation with the ezp= latform:installcommand, however which options you may install depen= ds on your distribution:

=20

# To do a clean install of "ezplatform":
$ php -d memory_limit=3D-1 app/console ezplatform:install --env=3Dprod clea=
n

# To do a clean install of "ezstudio":
$ php -d memory_limit=3D-1 app/console ezplatform:install --env=3Dprod stud=
io-clean

# If have "ezplatform-demo" or "ezstudio-demo" distribution, you may choose=
 to install demo instead:
$ php -d memory_limit=3D-1 app/console ezplatform:install --env=3Dprod demo=

=20

Password for the generated admin user is publish, this name and password is needed when you want to log in to backend UI.= Future versions will prompt you for a unique password during installation.=


 
If you get message "Unknown install type 'demo'" or similar=
, execute the following for possible options
php -d memory_limit=3D-1 app/console ezplatform:install --env=3Dprod -=
-help


 
5. Access your installation
You can now point your browser to the installation and browse the site. =
To access the  UI backend, use the /ez URL.

=20

=20

=20
=20
=20
=20
 
=20
=20
=20