- What is phisys/migrations-bundle used for?
- It is a PHP migrations bundle that provides structured, versioned database schema changes for arbitrary database engines. It helps keep schemas in sync across environments and deployments by tracking and applying migration steps. It is packaged as a framework bundle rather than a Laravel package.
- Is phisys/migrations-bundle compatible with Laravel?
- No, it is not a native Laravel package. It is a PHP migrations bundle built for bundle-style frameworks, typically Symfony. Laravel applications use their own migration system with service providers and Artisan commands. Bridging it into Laravel would require custom integration and is not a supported path.
- How do I install phisys/migrations-bundle?
- Install it with Composer using composer require phisys/migrations-bundle, then register the bundle in a compatible framework application. In Symfony you enable it in the kernel or bundles configuration. Laravel's package auto-discovery will not register it for you.
- Which database engines does phisys/migrations-bundle support?
- The package is described as providing migrations for arbitrary engines, meaning it is not tied to a single database vendor. Actual support depends on the database abstraction layer and drivers you configure. Check the repository's requirements and your target engine before committing.
- How does phisys/migrations-bundle compare to Laravel migrations?
- Laravel migrations are tightly integrated with Eloquent, Artisan, and Laravel's schema builder. phisys/migrations-bundle is designed for bundle-based PHP applications rather than Laravel's ecosystem. If you are building a Laravel app, Laravel's native migrations are usually the simpler and better-supported choice.
- Can phisys/migrations-bundle keep databases in sync across environments?
- Yes, that is its stated purpose: managing schema changes in a structured, versioned way so environments and deployments stay consistent. You still need a deployment process that runs the migrations in the right order. Always back up production data and test migrations against a copy first.
- How do I run migrations with phisys/migrations-bundle?
- Execution is typically through the host framework's console integration, not Laravel's Artisan migrate command. You register the bundle and use its provided commands or service to apply pending migrations. Exact command names depend on the version and framework integration.
- Is phisys/migrations-bundle actively maintained and safe for production?
- Maintenance activity should be verified on GitHub and Packagist before adopting it, including the latest release date and open issues. Check that it supports your PHP version and framework version. For production, pin a tested version and include migration rollback and backup steps.
- What are good alternatives to phisys/migrations-bundle?
- For Laravel, the built-in migrations are the default and best-supported option. Outside Laravel, Doctrine Migrations, Phinx, and Flyway or Liquibase are common choices. Choose based on framework integration, database support, and team familiarity.
- Can I test phisys/migrations-bundle migrations before running them in production?
- Yes, run them against a disposable database in local or CI environments and review the resulting schema. Use a staging database that mirrors production as closely as possible. Capture the generated SQL where possible and verify rollback behavior.