SeAT - forum: Seeders in V5 Plugins - Page 1

What's the best way to get seeders to initialize in V5 Plugins? I followed the doc, added the seeder file and included it in the ServiceProvider, but it didn't get run. It seems only the baked-in eveseat-org seeders are actually being run on every init of the docker services. What's the correct and working path for adding my jobs to a schedule when a Seat V5 instance uses my plugin?

I also see things like warlof's connector plugin just using a Migration file in order to add records to the Schedules table, and this seems odd to me.

NVM, this was working I was checking the logs from worker instead of front (web) where this is actually run.