Run seeds with migrations together without truncating all tables.

I don't think there is any reason you cant just call the seeder from the migration.

@rdelorier It is just one example. I have a database in production. With my new migrations I want run his associated seeders automatically.

So should the seeder run every time the migration runs or do you just want to specify the seeder so you done mess up the entire database?

If you need the to seed after a migration then that seed is part of the migration and should be fired by the migration itself.

note that you can specify a specific seeder class when you run php artisan db:seed --class=NewDataSeeder

public function up()
{
    //schema migrations here

    //now the data migration
    Artisan::call('db:seed', [
        '--class' => MigrationSpecificSeeder::class,
    ]);
}

Excuse me, I not see your previous answer. That is what I want!.

Yes, in production, when I deploy, I want to do (example): php artisan migrate .Then, if my new migrations has associated seeders (for example, 3 new tables with initial data, I want than run migrations and seeders, and not only migrate and I run seeder one, run seeder two...run seeder 'n' after one by one.

@rdelorier thanks, is perfect this solution.

Now, other question. Would the following correct?. For example, I need insert new data in a table with 7 rows. Is correct create a migration only for call a seeder with new inserts?.

I would use use a seeder for sure just because if you don't then you won't be able to add the rows unless you run the migration each time you seed.