Gacela

Appearance

View Markdown

Framework integration ​

Gacela runs beside Laravel or Symfony rather than replacing them. The host framework owns HTTP, console, and lifecycle integration; Gacela owns module boundaries. Bridge only the services that cross between those responsibilities.

Where to bootstrap

  • Symfony — public/index.php and bin/console
  • Laravel — bootstrap/app.php

Example projects ​

Cloneable minimal integrations:

Laravel ​

Bootstrap Gacela in bootstrap/app.php, then call module Facades from Laravel entry points. Keep Laravel services behind interfaces registered through bindings. The Laravel example contains the complete setup.

Symfony ​

Symfony bridge preview ​

The bridge teaches Symfony's container to honor Gacela's #[Inject] attribute on Symfony-managed commands and controllers.

Preview, not an installable release

gacela-project/symfony-bridge currently lives in the Gacela repository and is not published on Packagist. Do not add it to production Composer requirements yet. The stable approach is constructor injection with services explicitly shared between the two containers.

When evaluating the bridge from the monorepo, register its compiler pass in the kernel or bundle:

php
use Gacela\SymfonyBridge\GacelaInjectCompilerPass;
use Symfony\Component\DependencyInjection\ContainerBuilder;

final class AppKernel extends Kernel
{
    protected function build(ContainerBuilder $container): void
    {
        $container->addCompilerPass(new GacelaInjectCompilerPass());
    }
}

At compile time, the pass rewrites #[Inject] constructor parameters to resolve through Gacela. It rejects parameters that already have an explicit Symfony argument, preventing ambiguous ownership.

See the Inject attribute page for the full #[Inject] reference.

Share Symfony's Doctrine EntityManager ​

Bind EntityManagerInterface::class to Symfony's managed service so Gacela modules share the same connection and transactions:

php
<?php # public/index.php

// ...
$kernel = new \App\Kernel($_SERVER['APP_ENV']);

Gacela::bootstrap($appRootDir, function (GacelaConfig $config) use ($kernel) {
    $config->addBinding(ProductRepositoryInterface::class, ProductRepository::class);

    $config->addBinding(
        EntityManagerInterface::class,
        static fn () => $kernel->getContainer()->get('doctrine.orm.entity_manager'),
    );
});
// ...

Modules that type-hint EntityManagerInterface now receive Symfony's managed instance. Symfony remains responsible for its lifecycle and configuration.