- How do I install drfraker/snipe-migrations in a Laravel app?
- Install it with Composer using composer require drfraker/snipe-migrations. The package supplies Laravel migration files for Snipe-IT tables, so review the README and composer.json constraints before running php artisan migrate. Verify PHP and illuminate/database compatibility in a branch or disposable database first.
- What does drfraker/snipe-migrations actually do?
- It provides ready-to-use Laravel migration files for the Snipe-IT database schema. The package is aimed at helping PHP applications set up and manage Snipe-IT tables with maintainable migrations, and its description highlights blazing fast migrations for Laravel tests. It is not a full Snipe-IT application replacement; it focuses on schema migration files.
- Is this package for running Snipe-IT migrations in Laravel tests?
- Yes, the package description explicitly targets blazing fast database migrations for Laravel tests. It provides migration files for Snipe-IT tables so test suites can build the schema without hand-writing every migration. Confirm your test database driver and Laravel version constraints before relying on it in CI.
- Which Laravel versions are supported by drfraker/snipe-migrations?
- The available assessment only references a v1.4.0 release note that adds Laravel 8 support, and it does not provide exact composer.json PHP or illuminate/* constraints. Laravel 9 and later are not confirmed by the supplied context. Check the repository's composer.json and run the migrations in a test app before assuming support.
- Does drfraker/snipe-migrations support Laravel 9, 10, 11, or 12?
- The supplied context does not confirm support for Laravel 9, 10, 11, or 12. The only version-specific signal is a v1.4.0 note about Laravel 8 compatibility. Treat newer Laravel versions as unverified until you inspect composer constraints and CI evidence.
- Can I use these Snipe-IT migrations in production Laravel applications?
- You can use the migration files in production only after reviewing them for your Snipe-IT schema and operational needs. The assessment recommends pinning the package version, testing against a disposable database, and promoting through staging before production. If migrations affect reference data, confirm idempotency and coordinate a release window.
- How do I test that the package migrations work with my Laravel test suite?
- Run the package migrations against a disposable test database using Laravel's RefreshDatabase or DatabaseMigrations traits. Verify that all expected Snipe-IT tables, indexes, and foreign keys are created, and run the suite in CI. If your setup also uses seeders, check namespaced seeder classes and factory resolution for Laravel 8-era behavior.
- What are alternatives to drfraker/snipe-migrations?
- Alternatives include using Snipe-IT's own schema or migrations directly, writing custom Laravel migrations for the subset of tables you need, or loading a database schema dump for fast tests. Another schema-focused package could work if it declares support for your Laravel version. Compare maintenance activity and Composer constraints before switching.
- Is drfraker/snipe-migrations actively maintained?
- The assessment describes v1.4.0 as a compatibility release that merged two community PRs, which suggests limited maintainer capacity and potentially thin regression coverage. No repository history, release cadence, or test coverage was provided. Track releases and issues, and budget for a fork or replacement if the package lags supported Laravel versions.
- What risks should I check before adopting drfraker/snipe-migrations?
- Before adopting it, verify exact PHP and illuminate/* constraints, backward compatibility with Laravel 6 and 7, and whether Laravel 9+ works at runtime. Check test coverage, CI, changelog, seeder namespace behavior, and database driver support. Pin the version and validate migrations and seeders in staging before production.