README

Seed once. Roll back deliberately.

SuperSeeder gives Laravel seeders migration-like execution tracking without introducing a second command workflow. Mark a seeder as trackable and continue using Laravel's familiar make:seeder and db:seed commands.

Why SuperSeeder?

• Skip seeders that have already completed successfully.
• Keep a batch history in seeder_executions.
• Roll back the latest batch in reverse order.
• Preview rollbacks before modifying data.
• Block rollbacks when declared seeded records have foreign-key dependants.
• Keep destructive operations behind confirmation and environment safeguards.

Requirements

• PHP 8.2+
• Laravel 12 or 13

Installation

composer require riftweb/superseeder
php artisan migrate

The migration creates the seeder_executions tracking table.

Quick start

Generate a trackable seeder:

php artisan make:seeder PaymentMethodSeeder --trackable

By default, SuperSeeder prefixes the generated file name with a timestamp, for example database/seeders/20260901144500PaymentMethodSeeder.php. The seeder class name stays PaymentMethodSeeder.

Add its normal seed and rollback behavior:

<?php

namespace Database\Seeders;

use Illuminate\Database\Seeder;
use Riftweb\SuperSeeder\Traits\Trackable;

class PaymentMethodSeeder extends Seeder
{
    use Trackable;

    protected function up(): void
    {
        // Create your records.
    }

    public function down(): void
    {
        // Remove only the records created by this seeder.
    }
}

Call it from DatabaseSeeder as you would any Laravel seeder:

public function run(): void
{
    $this->call([
        PaymentMethodSeeder::class,
    ]);
}

Now seed normally:

php artisan db:seed

SuperSeeder records the successful run. Subsequent db:seed executions skip that seeder automatically.

Commands

--fresh and --clear ask for confirmation. Outside the local environment, they also require --force.

Safe rollbacks

A rollback calls each seeder's down() method and deletes its tracking record. Write down() defensively: target only records the seeder owns, never broad tables or shared data.

SuperSeeder can identify foreign-key dependants before calling down(). Return the primary keys your seeder created from seededRecords():

public function seededRecords(): array
{
    return [
        'users' => [
            'id' => [1, 2],
        ],
    ];
}

If another table references those records, rollback stops with an explanation. Use --cascade only when deleting the detected dependant records is safe. It deletes those records before calling the seeder's down() method:

php artisan db:seed --rollback --dry-run
php artisan db:seed --rollback --cascade

Rollbacks require --force outside local environments. In production, they are disabled unless explicitly enabled:

// config/superseeder.php
return [
    'rollback' => [
        'production_enabled' => true,
    ],
];

Configuration

Publish the configuration when you need to customize it:

php artisan vendor:publish --tag=superseeder-config

return [
    'bypass' => false,
    'table' => 'seeder_executions',
    'use_timestamped_seeders' => true,
    'rollback' => [
        'production_enabled' => false,
    ],
];

Set SUPERSEEDER_BYPASS=true only for an intentional emergency rerun. Prefer the one-off --rerun option for routine use.

Set SUPERSEEDER_USE_TIMESTAMPED_SEEDERS=false if you prefer generated trackable seeders without the timestamp prefix.

Testing

composer test

The GitHub Actions workflow tests Laravel 12 and 13 compatibility and checks code formatting on every push and pull request.

Laravel Boost

SuperSeeder includes AI guidelines and a seeder-development skill for Laravel Boost. After installing the package, import them with:

php artisan boost:install

To discover package resources after Boost has already been installed, run:

php artisan boost:update --discover

License

SuperSeeder is open-sourced software licensed under the MIT license.

Crafted with ❤️ by RIFT | Web Development