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

DEV: Add skip seed flag #10116

Merged
merged 7 commits into from Jun 25, 2020
Merged

DEV: Add skip seed flag #10116

merged 7 commits into from Jun 25, 2020

Conversation

oblakeerickson
Copy link
Member

Sometimes we don't want seed data to run like when running our post_deploy tasks. The seed data has already ran so we don't need to run it a second time.

@tgxworld
Copy link
Contributor

This looks good to me 👍

SeedFu.seed(seed_paths)
if ENV['SKIP_SEED'] != '1'
puts "Seeding #{db}"
SeedFu.seed(seed_paths)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually can we fold this into the Discourse.skip_post_deploy_migrations check below?

@eviltrout eviltrout added the 2.6 label Jun 24, 2020
@oblakeerickson oblakeerickson merged commit 01b6349 into master Jun 25, 2020
@oblakeerickson oblakeerickson deleted the db-migrate-debug branch June 25, 2020 16:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
3 participants