Weave Code
Pimcore Simple Migration Laravel Package
gal-digital-gmbh/pimcore-simple-migration
A lightweight migration helper for Pimcore that lets you version and apply database or data changes through simple, readable PHP migration files, with a straightforward CLI workflow for running and rolling back migrations across development and production environments.
At a glance
Frequently asked questions about Pimcore Simple Migration
- Is gal-digital-gmbh/pimcore-simple-migration a Laravel package or a Pimcore bundle?
- It is a Pimcore bundle, not a Laravel package. Pimcore is a Symfony-based PIM/DXP/MDM platform, so the bundle integrates with Pimcore's console and bundle registration rather than Laravel's Artisan or service provider system. If your application is Laravel, this package has no architectural fit and should be rejected.
- How do I install pimcore-simple-migration in a Pimcore project?
- Install it with Composer and register the bundle in your Pimcore bundle configuration, typically config/bundles.php. Before installing, read composer.json to confirm the Pimcore, Symfony, PHP, and Doctrine migration constraints it requires. Then verify the console commands appear and that the bundle does not collide with any existing migration metadata table.
- Which Pimcore and PHP versions does this migration helper support?
- The evaluation context points to Pimcore 10.x and 11.x on Symfony 5.4 or 6.4, with PHP 8.1 through 8.3 for Pimcore 11. You should confirm the actual supported matrix in composer.json rather than relying on prose in the README. Pin the Pimcore major version, PHP version, Symfony version, and transitive doctrine/migrations constraint for a schema-mutating dependency.
- How do I run and roll back migrations from the Pimcore console?
- The package provides a straightforward CLI workflow for running and rolling back migrations through simple PHP migration files. The exact command names and options should be taken from the repository README, since they are not fully reproduced here. Always exercise the run and rollback paths in a throwaway Pimcore skeleton before using them on shared or production databases.
- Does pimcore-simple-migration support down() rollbacks or is it forward-only?
- The overview says the CLI workflow supports rolling back migrations, but you should verify whether your migration files can implement a working down() path and whether rollback is covered by tests. Migration tooling sits on a high-blast-radius deployment path, so confirm rollback behavior in a sandbox with a database snapshot. If rollback is unreliable, treat the tool as forward-only and plan backups accordingly.
- Does it wrap doctrine/doctrine-migrations-bundle or ship its own migration runner?
- It appears to be a thin ergonomic wrapper over Doctrine Migrations intended to reduce boilerplate, but this needs to be confirmed from source before adoption. The key risk is running two migration runners or two metadata tables in one Pimcore project, which is a defect waiting to happen. If you already use doctrine-migrations-bundle directly, evaluate this as a replacement decision rather than an addition.
- Can it manage Pimcore class definitions, object bricks, field collections, or translations?
- The package is described as a helper for database or data changes through PHP migration files, so it likely handles schema and data operations rather than Pimcore's code-as-config class definitions. Pimcore class definitions, object bricks, field collections, and translations can drift independently of the database schema. Confirm explicitly whether those Pimcore-specific constructs are in scope or need a separate deployment step.
- Is this package safe to use for production database migrations?
- The technical assessment flags elevated supply-chain risk: zero stars, zero dependents, and no community validation for a component that mutates production schema. Use it only after a source audit, a sandbox install, and a functional spike on development with backups and staging checks. Pin all version constraints and consider a fork-and-vendor approach if the project is not actively maintained.
- How should I test pimcore-simple-migration before applying it to production?
- Start with a throwaway Pimcore skeleton and run the install and bundled commands against an empty database to confirm the console still works. Then do a functional spike on development with one representative migration and its rollback, checking whether Pimcore caches and definition caches are cleared after applying. Gate production behind a staging run and a verified database backup.
- Is pimcore-simple-migration maintained, and what are the alternatives?
- Check the repository for commit recency, tagged releases, open issues, CI status, and test coverage, because those are the cheapest proxies for a maintained versus abandoned utility. The alternatives are using doctrine/doctrine-migrations-bundle directly, borrowing useful conventions from this package, or maintaining a reviewed fork if you need its ergonomics. If there are no commits in 12 months, move directly to a fork-and-vendor evaluation rather than adopting it as-is.
Weaver
How can I help you explore Laravel packages today?