fix: seeder idempotent with firstOrCreate
Use firstOrCreate instead of create so db:seed can run safely on container restart without duplicate key violation.
This commit is contained in:
Use firstOrCreate instead of create so db:seed can run safely on container restart without duplicate key violation.