- Is saelker/migrations-bundle a Laravel package?
- No. It is a Symfony bundle that integrates Doctrine Migrations, and Laravel does not have a bundle system. Laravel cannot load or register a Symfony bundle through its service provider model. For a Laravel codebase, the architecture fit is effectively zero out of the box.
- Can I install saelker/migrations-bundle in a Laravel app with Composer?
- Composer may install the package, but it will not function as a Laravel package. It expects Symfony kernel and dependency injection container integration plus bundle registration. There is no Laravel service provider and no artisan commands are provided.
- What does saelker/migrations-bundle actually do?
- It provides Symfony console commands and configuration for Doctrine Migrations. It helps generate, run, and track database schema changes across multiple Symfony bundles. Its stated purpose is cross-bundle migration orchestration in Symfony, not Laravel's flat database/migrations model.
- Which Laravel versions does saelker/migrations-bundle support?
- None officially. The package is a Symfony bundle with no Laravel support story. Its last release was August 2023 and it targets Symfony, not Laravel 10 or Laravel 11. Do not expect compatibility with any Laravel version.
- How is saelker/migrations-bundle configured in a Laravel project?
- It is not configurable through Laravel config files or publishable package config. Configuration happens through Symfony bundle and Doctrine Migrations settings. Laravel has no equivalent bundle registration or compiler pass mechanism, so there is nothing to wire up in config/app.php.
- How do I run migrations for multiple packages in Laravel instead?
- Use loadMigrationsFrom() in each package service provider and prefix migration filenames to control ordering. Laravel's artisan migrate handles discovery, the migrations table, and batching natively. This covers most multi-package migration needs without a Symfony bundle.
- Is saelker/migrations-bundle maintained and safe for production?
- Adoption is very low, with roughly 2 stars and 0 dependents, a single author, and a last release in August 2023. There is no evidence of a security or compatibility maintenance cadence. Adding it to a deployment-critical migration path is a poor trade because silent migration failures can corrupt production data.
- Can I use Doctrine Migrations with Laravel?
- Doctrine Migrations can be bridged into Laravel through community packages, but saelker/migrations-bundle is not one of those bridges. It is built around Symfony's bundle lifecycle and console commands. For Laravel, prefer native migrations or a dedicated Laravel-Doctrine integration.
- Should I fork saelker/migrations-bundle to port it to Laravel?
- Forking would mean reimplementing its discovery and ordering logic as a Laravel service provider and custom migrator. At that point you inherit only the design idea, not the code, and you own maintenance and compatibility risk. Building a native equivalent is usually cheaper than owning a fork.
- How would I test saelker/migrations-bundle in a Laravel application?
- You cannot meaningfully test it in Laravel because it depends on the Symfony kernel and Symfony console. There are no Laravel test helpers or factories for its commands. For Laravel, test native migrations with RefreshDatabase and standard artisan migrate assertions instead.