Skip to content

Install eZ Enterprise

Enterprise

To install eZ Enterprise, follow the procedure described in Install eZ Platform. Because you do not have access to the Enterprise GitHub repositories, you need to download an archive from the Support Portal.

There are a few special steps you need to take when installing eZ Enterprise:

Setting up authentication tokens for eZ Enterprise

eZ Enterprise subscribers have access to commercial packages at updates.ez.no/bul/. The site is password-protected. You will need to set up authentication tokens to get access to it.

Log in to your service portal on support.ez.no and look for the following on the "Maintenance and Support agreement details" screen:

Authentication token

  1. Select "Create token" (this requires the "Portal administrator" access level).
  2. Fill in a label describing the use of the token. This will allow you to revoke access later.
  3. Save the password, you will not get access to it again!

Save authentication token in auth.json to avoid repeatedly typing it

Composer will ask to do this for you on updates. If you decline, you can create an auth.json file manually in one of the following ways:

  • A: Store your credentials in the project directory (for security reasons do not check it in to git):
1
composer config http-basic.updates.ez.no <installation-key> <token-password>
  • B: If you only have one project on the machine/server/vm, and want to install globally in COMPOSER_HOME directory for machine-wide use:
1
composer config --global http-basic.updates.ez.no <installation-key> <token-password>

After this, when running Composer to get updates, you will be asked for a username and password. Use:

  • as username – your Installation key found on the "Maintenance and Support agreement details" page in the service portal
  • as password – the token password you retrieved in step 3.

Authentication token validation delay

You can encounter some delay between creating the token and being able to use it in Composer. It might take up to 15 minutes.

Support agreement expiry

If your Support agreement expires, your authentication token(s) will no longer work. They will become active again if the agreement is renewed, but this process may take up to 24 hours. (If the agreement is renewed before the expiry date, there will be no disruption of service.)

Usage of authentication token with composer create-project

If you have several projects set up on your machine, they should all use different tokens set in auth.json file in project directory.

But in order to install a new project using composer create-project to get latest version of eZ Enterprise, you'll need to tell Composer which token to use before the project folder is created in the first place. This can be done in the following way:

1
COMPOSER_AUTH='{"http-basic":{"updates.ez.no":{"username":"<installation-key>","password":"<token-password>"}}}' composer create-project --keep-vcs ezsystems/ezplatform-ee my-new-ee-project

Enable Date-based Publisher

To enable delayed publishing of Content using the Date-based Publisher, you need to set up cron to run the command bin/console ezstudio:scheduled:publish periodically.

For example, to check for publishing every minute, add the following script:

echo '* * * * * cd [path-to-ezplatform]; php bin/console ezplatform:cron:run --quiet --env=prod' > ezp_cron.txt

For 5-minute intervals:

echo '*/5 * * * * cd [path-to-ezplatform]; php bin/console ezplatform:cron:run --quiet --env=prod' > ezp_cron.txt

Next, append the new cron to user's crontab without destroying existing crons. Assuming the web server user data is www-data:

crontab -u www-data -l|cat - ezp_cron.txt | crontab -u www-data -

Finally, remove the temporary file:

rm ezp_cron.txt

Read the Docs