Commit

e411aba

I'm prepping a deploy that has migrations that take 7 minutes on my localhost. I hope I can still deploy with Laravel Envoyer, it's going to be close! I might need to move some of the data from migrations to artisan commands, but it's data that I don't expect to update often, so…
I don't get it. Once your migration ran, it's done. Why does it matter if the data is updated often after migrating? Regardless, I've done migrations in artisan commands if 1. they were backwards compatible and/or 2. they took more than a few seconds.
The data import is currently in the long-running migrations. It might be smarter to remove the data import from the migrations and put it into an Artisan command, especially if I ever plan to change the data in the future.

commit e411aba