The content repository is where all your content is been stored. It is the heart of eZ Publish which you interact with using Public 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.
Following configuration examples are compatible with eZ Publish 5.3 / 2014.03
Using default values
If no repository is specified for a siteaccess or siteaccess group, the first defined repository (under
ezpublish.repositories) will be used.
Legacy storage 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.
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
Limit of archived Content item versions
default_version_archive_limit controls the number of archived versions per Content item that will be stored in the repository, by default set to 5. This setting is configured in the following way (typically in
This limit is enforced on publishing a new version and only covers archived versions, not drafts.