| Version | Date | Notes | By |
|---|---|---|---|
| 0.2 | 2018-03-02 | This is no longer used | JFM |
| 0.1 | 2018-01-05 | Initial release | FPA |
This is no longer used - Seeds are now part of normal migrations
Seeding as it is currently done in Laravel is intended only for dev builds, but what if you're iteratively creating your database and want to constantly flush it and repopulate it during development? What if you want to seed a production database with different data from what you use in development? What if you want to seed a table you've added to a database that is currently in production with new data?
php artisan seed will only run seeds that haven't already been run.php artisan db:seed
or
php artisan migrate:refresh --seedphp artisan seed:run --file=seed_2015_05_27_030017_UserSeederWhen you install Gardener, various artisan commands are made available to you which use the same methodology you're used to using with Migrations.
| seed:run | Runs all the seeds in the smartSeeds directory that haven't been run yet. |
| seed:make | Makes a new seed class in the environment you specify. |
| seed:rollback | Rollback doesn't undo seeding (which would be impossible with an auto-incrementing primary key). It just allows you to re-run the last batch of seeds. |
| seed:reset | Resets all the seeds. |
| seed:refresh | Resets and re-runs all seeds. |
| seed:install | You don't have to use this... it will be run automatically when you call "seed" |
"wemake/laravel-gardener": "^1.0" to your composer.json and run an update to bring it in (or run composer require wemake/laravel-gardener).WeMake\Gardener\GardenerServiceProvider::class to your providers array in app/config/app.phpphp artisan vendor:publish to push config files to your config folder if you want to override the name of the seeds folder or the name of the table where seeds are stored