Weave Code
Mandango Bundle Laravel Package
mandango/mandango-bundle
MandangoBundle integrates the Mandango MongoDB ODM with Symfony, providing bundle configuration, document mapping, repository services, and event integration for PHP applications backed by MongoDB. It streamlines setup and service wiring for Mandango documents within Symfony projects.
Bundle to use Mandango with Symfony2
Frequently asked questions about Mandango Bundle
- Can I use mandango/mandango-bundle in a Laravel application?
- No. MandangoBundle is a Symfony2 bundle with a MandangoBundle class, DependencyInjection/MandangoExtension.php, YAML configuration under the mandango key, and mandango:generate console commands. Laravel's container, config repository, and Artisan consume none of that, and there is no Illuminate\Support\ServiceProvider, facade, publishable config, or package discovery entry. Dropped into a Laravel codebase the bundle is inert; only the upstream mandango/mandango core library is theoretically callable if you hand-write connection wiring, metadata loading, and model generation.
- How do I install mandango/mandango-bundle?
- You would normally require it with Composer and register the bundle in a Symfony2 AppKernel, then configure it under the mandango key. That installation path is Symfony-specific and does not produce a working Laravel integration. The package also depends on the legacy ext-mongo driver, so a modern PHP runtime cannot load it as shipped. For Laravel, installing it is not a supported or useful step.
- Is mandango/mandango-bundle compatible with PHP 7 or PHP 8?
- No. Mandango targets the legacy ext-mongo extension and its MongoClient and MongoCollection classes, which were removed in PHP 7. The replacement ext-mongodb extension has an incompatible API, so supporting PHP 7 or PHP 8 would require a driver-layer rewrite, not a patch. At PHP 7.0 or later the package is unusable as shipped.
- Does mandango/mandango-bundle support Laravel 10 or Laravel 11?
- No Laravel version is supported, including Laravel 10 and Laravel 11. The package is built for Symfony 2.x, which reached end of life in 2018, and it has no Laravel service provider, facade, config publishing, or package discovery. Its console commands are Symfony commands, not Artisan commands, so Laravel cannot consume them.
- How is mandango/mandango-bundle configured, and can I publish its config in Laravel?
- Configuration is Symfony YAML under the mandango key, processed by DependencyInjection/MandangoExtension.php and wired into Symfony's service container. There is no publishable Laravel config file and no config/mandango.php to publish with vendor:publish. You would have to rebuild the connection, metadata, and repository wiring manually in Laravel, which is a port rather than an installation.
- How does Mandango document mapping work compared with Eloquent?
- Mandango is a code-generating ODM. You author XML or PHP schema definitions, run Mondator at build time to emit model, repository, and query classes, then consume those generated classes through a connection and unit-of-work API. There is no Eloquent analogue, and adopting it means running a second persistence paradigm beside Eloquent, with its own codegen stage in CI and generated artifacts under version control.
- Is mandango/mandango-bundle still maintained?
- No. Mandango has been unmaintained for roughly a decade, Symfony 2.x went end of life in 2018, and the repository has about 25 stars and zero dependents. There are no security patches, no PHP compatibility work, and no upstream triage. That combination makes it unsuitable for new development.
- What are the best Laravel alternatives to MandangoBundle for MongoDB?
- For Laravel, use ext-mongodb plus the official mongodb/mongodb driver on top of mongodb/laravel-mongodb, which preserves Eloquent idioms with near-zero ramp-up. If you need a document-mapper style, doctrine/mongodb-odm is the maintained option. Both are PHP 8 compatible and staffable; Mandango offers nothing they do not and lacks everything they do.
- Can I use mandango/mandango-bundle in production?
- Not for new work. The critical risks are the removed ext-mongo driver, the unmaintained lifecycle, and the lack of an installed base or community validation. If a legacy Symfony2 application already runs Mandango, freeze it, pin exact versions, vendor dependencies, and do not lift the bundle into Laravel. Fund an exit plan instead.
- How do I test a MandangoBundle application, and how do I migrate it to Laravel?
- There is no Laravel testing integration for MandangoBundle; tests in a legacy app depend on a Symfony2 kernel and the removed ext-mongo driver. For migration, do not port the bundle: export data with the modern mongodb/mongodb driver, remodel it in the target layer, and cut over read paths before write paths. For a data-only move, a one-time ETL script against mongodb/mongodb is the practical route. For greenfield Laravel, adopt mongodb/laravel-mongodb instead.
Weaver
How can I help you explore Laravel packages today?