Message-ID: <1825503733.3070.1485851862699.JavaMail.confluence@ip-10-127-227-164> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_3069_677577360.1485851862699" ------=_Part_3069_677577360.1485851862699 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html Content Repository configuration

Content Repository configuration

=20 =20

The content repository is where all your content is bee= n stored. It is the heart of eZ Publish which you interact with using Publi= c API.

To store data, the content repository uses a storage engine, that can virtually can work with any kind of storage (RDBMS, NoSQL...= ). eZ Publish 5 comes with a relational storage engine, compatible with v4.= x: the Legacy storage engine, which is the default.

You can define several repositories within a single application. However= , you can only use one per site.

Version compatibility

Following configuration examples are compatible with eZ Pub= lish 5.3 / 2014.03

Configurati= on examples

Using default = values

ezpublish.yml
=20 
ezpublish:
    repositories:
        # Defining repository with alias "main"
        # Default storage engine is used, with default connection
        # Equals to:
        # main: { engine: legacy, connection: <defaultConnectionName>=
 }
        main: ~

    system:
        # All members of my_siteaccess_group will use "main" repository
        # No need to set "repository", it will take the first defined repos=
itory by default
        my_siteaccess_group:
            # ...
=20

If no repository is specified for a siteaccess or siteaccess group, the = first defined repository (under ezpublish.repositories) will b= e used.

All explicit

ezpublish.yml
=20 
doctrine:
    dbal:
        default_connection: my_connection_name
        connections:
            my_connection_name:
                driver:   pdo_mysql
                host:     localhost
                port:     3306
                dbname:   my_database
                user:     my_user
                password: my_password
                charset:  UTF8

            another_connection_name:
                # ...

ezpublish:
    repositories:
        first_repository: { engine: legacy, connection: my_connection_name,=
 config: {} }
        second_repository: { engine: legacy, connection: another_connection=
_name, config: {} }

    # ...

    system:
        my_first_siteaccess:
            repository: first_repository

            # ...

        my_second_siteaccess:
            repository: second_repository
=20

Legacy storag= e engine

As of eZ Publish 5.3, legacy storage engine uses Doctrine DBAL (Database Abstraction Layer).= Database settings are supplied by DoctrineBundle.= As such, you can refer to DoctrineBundle's documentation= .

ORM

Doctrine ORM is not provided by default. If you want to= use it, you will need to add doctrine/orm as a dependency in = your composer.json.

Limit of archived Content item versions

V5.4.10

default_version_archive_limit controls the number of archiv= ed versions per Content item that will be stored in the repository, by defa= ult set to 5. This setting is configured in the following way (typically in= ezpublish.yml):

=20 
ezpublish:
    repositories:
        default:
            options:
                default_version_archive_limit: 10
=20

This limit is enforced on publishing a new version and only covers= archived versions, not drafts.

 

 

------=_Part_3069_677577360.1485851862699--