4 ms·
Seeding development with production data is just lazy, unnecessary, and, as we see here, dangerous. Spend some resources on a proper seeding setup.
by rhizome 11y ago
Seeding development with production data is just lazy, unnecessary, and, as we see here, dangerous. Spend some resources on a proper seeding setup.
- voltagex_ 11y agoWhat would you suggest for such a setup? Also, I did not say seed it with production data - I mean jumble PII and then import a section of production data into dev. Sometimes this is necessary.
- thaumaturgy 11y agoA while back a fake DB data generator was posted to HN: https://news.ycombinator.com/item?id=8761953 https://news.ycombinator.com/item?id=8761953 Further back, there's also this one for Python: https://news.ycombinator.com/item?id=7102268 https://news.ycombinator.com/item?id=7102268 And this one for PHP: https://github.com/fzaninotto/Faker https://github.com/fzaninotto/Faker (there were no HN comments on that thread) And this one for Ruby: https://news.ycombinator.com/item?id=86018 https://news.ycombinator.com/item?id=86018 (also no comments) These seem like a good starting point. Also, mining bug reports for data that causes problems in your application is a lot of fun. You can turn your development database into a collection of pathological edge cases.