Using required seed task in production

Nobody has claimed this yet.

Lucky apps come with a task to generate required seed data as well as a task to generate sample seed data. We say that the required seed data is data required for your application to work properly.

Right now with how the task is, getting that task to run in production is a little tricky. We automatically require the factories which live in your specs. If you use Faker, or some other development dependency, then the task won't compile for production. Granted, you're most likely to only ever run this task once for production, but you may also need to run it for staging a few times, and maybe a QA or something...

It seems it would make sense that if you stood up a french new Lucky app, and deployed to production, that this task would be available t o you with little work. I'm not sure what the cleanest way to do that is, but we could set it up as a precompiled task or something.

Start by tracing the generated required and sample seed tasks and how factories in specs are automatically required. Check production compilation when Faker or other development dependencies are referenced, including the staging and QA use cases. Done means required seed data can be run after deployment without those dependencies.

Written by the indexing model from the issue text.