README

[Deprecated]

Use prooph symfony bundles instead

Overview

This Symfony bundle creates two services to have support for "container-interop" in your Symfony application.

Why?

Well, we at prooph software GmbH create framework agnostic factories/libraries and don't want to configure for each Framework new factories or service container. The factories are based on the container-interop specification and need an service config in the container to retrieve different component configuration.

See prooph-bundle project to get started out of the box with message bus, CQRS, event sourcing and snapshots of the prooph components.

Configuration

In your parameters.yml you can define the key interop_config with a list of Symfony bundles where it's configuration should be put into the config service. This bundle provides the default value prooph, so the prooph component config can be used out of the box. It's also possible to add more values to the list, see this example

parameters:
    # other parameters in your parameters.yml
    interop_config: ['prooph', 'awesome_bundle', 'acme_bundle']

Available services

• interop_container: Simple container-interop wrapper around the Symfony Symfony\Component\DependencyInjection\ContainerInterface
• config: Contains the bundle configuration which is used by the factories

Installation

You can install prooph/prooph-interop-bundle via composer by adding "proophsoftware/prooph-interop-bundle": "^0.1" as requirement to your composer.json.

Don't forget to enable this Bundle.

Support

• Ask questions on prooph-users mailing list.
• File issues at https://github.com/proophsoftware/prooph-interop-bundle/issues.
• Say hello in the prooph gitter chat.

Contribute

Please feel free to fork and extend existing or add new plugins and send a pull request with your changes! To establish a consistent code quality, please provide unit tests for all your changes and may adapt the documentation.

License

Released under the New BSD License.