Is just a question about laravel seeding, if I want to make my app portable, it is a good practice to save app-work-essential data in DatabaseSeeder
laravel class
?
If not? How could I do it?
Is just a question about laravel seeding, if I want to make my app portable, it is a good practice to save app-work-essential data in DatabaseSeeder
laravel class
?
If not? How could I do it?
Seeding is used to bootstrap the application. If the data is just enough to get the application up, seeding is the official way to do this; especially if you are in an environment using Continuous Integration/Deployment. The paradigm is that you, as developer, shouldn't have to have direct access to the database to install or update the application. I don't necessarily believe that needs to be true, but it is a nice ideal to shoot for, as it means the code will be more portable.
One very important exception is based on the idea that the seeder is typically versioned, so it shouldn't contain sensitive or private information. Things like real user password hashes (a temporary admin password is alright), HIPAA, FERPA, social security numbers, bank account information, etc. etc.