iseed ignores the --force and -n options in production mode!

[archfrog]

Hi,

I run a simple setup with some mostly static links that are updated once a week. They are stored in database both on the development box and on the production server. About once a month or so, I need to change the seeder to reflect changes in the set up mostly static links. After that, I need to do a reseed on both the development and production end.

When I run this command, in an SSH-controlled shell script on the production server, I get a prompt to verify that I want to do the seed:

./artisan db:seed -n --force

I thought the whole point of these two options (especially --force) was to DISABLE all prompts.

Thanks for your great work, though :-)

Cheers,
Archfrog

[archfrog]

Seems like I mistook the artisan migrate:fresh command for artisan db:seed. At least, I cannot recreate the problem now.

I'm closing this case.