Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Divide the seeders for production and testing #113

Open
troccoli opened this issue Jun 7, 2020 · 0 comments
Open

Divide the seeders for production and testing #113

troccoli opened this issue Jun 7, 2020 · 0 comments
Assignees
Labels
enhancement refactor unscheduled Issues that have not yet been put in a project

Comments

@troccoli
Copy link
Owner

troccoli commented Jun 7, 2020

The current seeders populate the database with testing data: users, seasons, clubs, etc.

However, part of that data is not actually test data. For example the Site Administrator role should always be added.

We should include in DatabaseSeeder only the seeder for actual production data. Then, create another seeder, TestSeeder or something, to add the test data.

Then the process would be

  • php artisan migrate:fresh --seed to create a production ready database
  • php artisan db:seed --class TestSeeder to add testing data
@troccoli troccoli added the unscheduled Issues that have not yet been put in a project label Jun 28, 2020
@troccoli troccoli self-assigned this Dec 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement refactor unscheduled Issues that have not yet been put in a project
Projects
None yet
Development

No branches or pull requests

1 participant