Laravel Turbo Seeder Laravel Package

Getting Started

• Install with composer require iz-ahmad/laravel-turbo-seeder and run the package discovery step if not using Laravel auto-discovery.
• Publish any package config (php artisan vendor:publish --tag=turbo-seeder-config) and inspect the production safety guard and status display options first.
• Discover the entry point with php artisan list | grep turbo or review vendor/iz-ahmad/laravel-turbo-seeder/src for the console command/seeder class.
• First use case: replace a slow db:seed workflow in local or staging with the package’s truncate-based seeding path, then confirm the new status display and production guard behave as expected.

Implementation Patterns

• Use the package for repeatable local/test database refreshes: truncate target tables, then run seeders in dependency order. This is especially useful before feature tests or demo environments.
• Keep the production safety guard enabled by default and rely on APP_ENV to block accidental production truncation. If production seeding is ever required, prefer an explicit opt-in flag or environment override rather than disabling the guard globally.
• In CI, run with APP_ENV=testing and consider disabling or quieting the status display if your logs need to stay machine-readable.
• For long seed runs, use the new status display to monitor progress and identify slow tables. This pairs well with Laravel’s verbose command output during debugging.
• Integrate with existing seeders by wrapping or extending the package’s seeder class, or by calling it from test setup. Keep truncation scoped to the tables your test suite owns to avoid crossing test boundaries.
• If your schema has foreign keys, verify the v1.0.0 truncate timing fix against your database driver. Use explicit seeder ordering and constraint handling where needed.

Gotchas and Tips

• Truncate is not delete: it bypasses model events, observers, and soft deletes. Do not use this package where application-level cleanup logic is required.
• The production safety guard may block execution in any environment Laravel considers production. Check APP_ENV and any package-specific allowlist before debugging “why did seeding stop?”
• The truncate timing fix likely handles constraint disabling/enabling around truncation, but database-specific behavior can still differ. Test with MySQL, PostgreSQL, and SQLite if you support multiple drivers.
• Status display can be noisy in CI or when piping output. Look for a config or command flag to disable it.
• v1.0.0 is a major release. Even though the visible release notes only mention features, pin the version and review the full changelog from v0.1.0 before upgrading existing projects.
• Debug truncation failures with verbose command output and by checking table order, foreign keys, and database user permissions. Truncate often requires stronger privileges than delete.
• Extension points to inspect first: package config, the main seeder/command class, and any status reporter or callback hooks. These are the safest places to customize behavior without forking.