Download the PHP package chubbyphp/chubbyphp-laminas-config-doctrine without Composer

chubbyphp-laminas-config-doctrine

Description

Service factories that wire Doctrine (DBAL, ORM and MongoDB ODM) into a PSR-11 container from plain array configuration. They follow the laminas/laminas-servicemanager dependencies convention, so they work with chubbyphp/chubbyphp-container through chubbyphp/chubbyphp-laminas-config, with Mezzio, and with any other container that understands the same configuration format (Aura.Di, Pimple, Auryn, Symfony, PHP-DI, ...).

What you get:

• Factories for the DBAL Connection, the ORM EntityManager, the MongoDB Client and the ODM DocumentManager, plus their Configuration and EventManager objects.
• Factories for the Symfony cache adapters Doctrine uses for metadata, query and result caching (array, APCu, chain, filesystem, memcached, PHP files, redis).
• A ClassMapDriver that lets you write mappings as small PHP classes instead of attributes, XML or YAML.
• Factories for the Doctrine console commands (schema tool, cache clearing, proxies, hydrators, ...) and dbal:database:create / dbal:database:drop commands.
• Support for multiple named connections, entity managers and document managers (for example read and write) from the same set of factories.

Services are registered under their class name (for example EntityManagerInterface::class) rather than under doctrine.something string keys, and only the Doctrine packages you actually use have to be installed.

The concept is based on dasprid/container-interop-doctrine by @DASPRiD, now maintained as roave/psr-container-doctrine.

Requirements

• php: ^8.3

Suggested

Install only what you need:

• For the ORM: doctrine/dbal: ^4.4.4 and doctrine/orm: ^3.6.8
• For the MongoDB ODM: doctrine/mongodb-odm: ^2.17.1 and mongodb/mongodb: ^1.21.4|^2.2.0

Installation

Through Composer as chubbyphp/chubbyphp-laminas-config-doctrine.

Then add the Doctrine packages for the storage you use:

Usage

Each factory reads its options from the doctrine section of the container configuration and only needs the dependencies.factories entry to be registered. A minimal ORM setup looks like this:

Good to know:

• Configuration values are resolved through the container. Any string value that matches a registered service name is replaced by that service, so 'metadataCache' => CacheItemPoolInterface::class injects the configured cache adapter. Keys under configuration map to setters on the Doctrine Configuration object (proxyDir calls setProxyDir()), so every option Doctrine offers is available.
• Dependencies are resolved lazily. The EntityManagerFactory looks up Connection::class, Configuration::class and EventManager::class in the container. If they are not registered, it builds them with the matching factory from this package, so you only register what you want to access directly.
• Multiple instances share the same factories. Register a factory as [EntityManagerFactory::class, 'read'] under the service name EntityManagerInterface::class.'read', and nest the related configuration under a read key. The factory then resolves all of its dependencies with the same read suffix.

MongodbODM

• Single connection
• Multiple connection

ORM

• Single connection
• Multiple connection

Console commands

Register the command factories from ServiceFactory\DBAL\Tools\Console\Command, ServiceFactory\ORM\Tools\Console\Command and ServiceFactory\ODM\MongoDB\Tools\Console\Command and add the resulting commands to your Symfony console application. The commands pick the right instance by name: --connection=<name> for DBAL, --em=<name> for the ORM and --dm=<name> for the MongoDB ODM. Without the option the default (unsuffixed) service is used.

Copyright

2026 Dominik Zogg