Database Seeders
Run individual or default database seeders from the admin UI.
Overview
Database Seeders shows each registered seeder’s status and lets admins queue runs (and re-runs) from the UI.
Where it lives
Route: /admin/settings/seeders (admin.settings.seeders)
Open Admin → System → Database Seeders. Requires admin access.
What the panel lists
The cards come from SeederPanelCatalog::withStatus(), the single source of truth shared with DatabaseSeeder:
- Boot-start seeders (
isDefault) — the ordered setphp artisan db:seedruns, countries through sample catalogue items. See Seeder reference for what each one creates. - VolumeTestSeeder — only appears when
SIGNALS_VOLUME_SEEDER=true, and is a load-testing tool rather than a demo.
Demo data is not a panel card. Seed and clear it from the CLI with php artisan signals:seed-demo and php artisan signals:clear-demo. Clearing is allowed in local and testing; every other environment, including production and staging, refuses unless the tenant is explicitly flagged as demo (instance.is_demo or flags.demo). Force flags cannot bypass this refusal. Self-hosted production installations have no tenant demo flag, so demo data seeded there cannot be cleared with this command. An eligible demo tenant outside local/testing additionally needs --force-demo-finance-purge to confirm finance removal. The command also refuses when demo finance history is linked to real data. See Seeders.
Each card shows the seeder's description, the items it creates, and a live Seeded / Not Seeded status derived from the database rather than a run log — so a seeder run outside the panel still reads as seeded.
Key workflows
- Run Default Seeders runs
DatabaseSeeder(every boot-start seeder plus the development owner account). It is highlighted when the permissions or roles seeders report Not Seeded — the minimum for a usable RBAC boot. - Individual Run/Re-run dispatches
RunSeederJobon theimportsqueue, with step-by-step progress polled from the cache. - The panel surfaces its own failure modes: it warns when a run sits queued with no worker on the
importsqueue, abandons it after a timeout, and reports a run whose progress entry disappears. - Seeder class list is locked — clients cannot inject arbitrary classes.
Reset database (owner only)
The Seeders page includes an owner-only Reset database card (hidden in production). It wipes every table, re-runs all migrations, and seeds only the boot-start reference data — no demo data. Everyone is signed out, including the owner who triggered it.
The card dispatches RunDatabaseResetJob on the imports queue, which runs php artisan signals:fresh --force (and --force-dev on a protected development database). A worker must be running.
The CLI equivalent is:
php artisan signals:fresh --force
On a protected development database, add --force-dev.
At a glance
Run database seeders to populate reference data. Each seeder shows its status (not run, completed, or available) and can be executed individually. Useful after initial setup or when adding new modules.
Related
- Get started: Seeders
- Seeder reference