- Is graviton/mongodb-migrations-bundle a Laravel package?
- No. graviton/mongodb-migrations-bundle is a Symfony bundle, and Laravel has no bundle concept. Its value is mostly Symfony dependency-injection wiring such as service definitions, compiler passes, and bundle registration. A Laravel integration would need a service provider and Artisan command around the underlying migration engine.
- Can I use graviton/mongodb-migrations-bundle with Laravel to manage MongoDB migrations?
- Not directly. The bundle's Symfony wiring is not reusable in Laravel, and the only reusable layer is the underlying graviton/mongodb-migrations engine. Viable paths are running the bundle as a sidecar CLI, extracting the engine behind an Artisan command, or forking and vendoring it. Each path has tradeoffs in runtime, configuration, and maintenance.
- How do I install graviton/mongodb-migrations-bundle in a Laravel app?
- You can run composer require graviton/mongodb-migrations-bundle, but Laravel will not auto-register it as a bundle or expose its commands. There is no Laravel package discovery or Artisan integration in the bundle itself. In practice you would need to build a wrapper, run it in an isolated Symfony container, or avoid it in favor of the underlying engine. Check composer.json constraints before attempting installation.
- What Composer dependencies and PHP or Symfony versions does graviton/mongodb-migrations-bundle require?
- The provided evaluation does not list exact constraints, but it warns that the bundle likely dates from the Symfony 2.x, 3.x, or 4.x era. PHP 8.x and Symfony 6 or 7 compatibility are unverified and unlikely to be maintained. The spike should read composer.json for exact Symfony, PHP, and extension requirements before adoption.
- Does graviton/mongodb-migrations-bundle require the legacy ext-mongo extension?
- That is a key unknown and a potential hard blocker. Migration bundles of this vintage often pin the removed ext-mongo extension instead of ext-mongodb plus mongodb/mongodb or alcaeus/mongo-php-adapter. Check composer.json and test installation on your target PHP runtime. If ext-mongo is required, the package will not run on modern PHP.
- Does graviton/mongodb-migrations-bundle work with mongodb/laravel-mongodb and Eloquent?
- The assessment says this tooling is built around Doctrine MongoDB ODM, while Laravel apps typically use mongodb/laravel-mongodb with Eloquent. Running both against the same collections is possible but creates two mapping conventions, two hydration behaviors, and potentially conflicting index and validation assumptions. That mismatch is a significant integration risk for Laravel teams.
- What is the underlying migration engine behind graviton/mongodb-migrations-bundle?
- The bundle wraps the separate graviton/mongodb-migrations library, which handles discovering, ordering, applying, and versioning migration classes against MongoDB. The bundle itself is mostly Symfony dependency-injection and console wiring. Before extracting it, confirm the engine has no Symfony coupling leaks such as container-bound factories, kernel.event_dispatcher usage, or PSR-11 assumptions.
- Are there alternatives to graviton/mongodb-migrations-bundle for Laravel MongoDB migrations?
- Laravel's native migrator is SQL-oriented and does not model MongoDB collection creation, JSON schema validators, or index management well. Teams often hand-roll MongoDB migrations or use mongodb/laravel-mongodb schema features with custom Artisan commands. Extracting the graviton engine is another option if the spike confirms it is framework-agnostic. Evaluate community packages by checking recent commits, dependents, and Laravel version support.
- Is graviton/mongodb-migrations-bundle maintained and safe for production?
- The metrics are a red flag: zero stars, zero dependents, and a score of 0. This is a single-vendor artifact with no visible community or third-party usage, so expect silent breakage rather than bug reports. Verify whether the repo is archived and whether there has been commit activity in the last 24 months. Treat production use as high risk without a fork or isolated sidecar approach.
- Does graviton/mongodb-migrations-bundle support rollbacks, versioning, and locking for concurrent runs?
- The assessment flags these as open questions for the spike. You need to confirm whether the engine uses a migrations collection with checksums and versioning or only blind up/down ordering. Also verify rollback semantics for down(), behavior after a partially applied migration, and whether a distributed lock prevents concurrent runs across multiple pods. Test index creation on large existing collections and confirm background or rolling index build support.