Load full dev seeds in Conductor workspaces via --seed-dev#1588
Merged
Conversation
bin/setup hardcoded `db:seed`, so Conductor workspaces only ever got the minimal base seeds and the UI came up empty of sample data. The dev sample set (workshops, events, analytics, profiles, payments, etc.) lives behind the `db:seed:dev` rake task, which nothing was invoking. Add a `--seed-dev` flag to bin/setup that swaps in `db:seed:dev` (it chains the base `db:seed` first), keeping plain `db:seed` the default for CI and lean setups, and pass it from bin/conductor-setup since Conductor workspaces are always dev. Also drops the redundant `npm ci` from bin/conductor-setup — bin/setup already runs it — and clarifies the surrounding comment. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
maebeale
commented
Jun 7, 2026
| # --seed-dev loads the full dev sample dataset (db:seed:dev chains the base | ||
| # db:seed first); plain db:seed stays the default for CI and lean setups. | ||
| if ARGV.include?("--seed-dev") | ||
| system! "bin/rails db:seed:dev" |
Collaborator
Author
There was a problem hiding this comment.
🤖 From Claude: db:seed:dev chains the base db:seed first, so this branch swaps the call rather than running both. Plain db:seed stays the default so CI and production-style setups skip the dev sample data.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is the goal of this PR and why is this important?
bin/setuphardcodedbin/rails db:seed, which only loads the minimal base seeds (db/seeds.rb). The rich dev dataset lives behind thedb:seed:devrake task, and nothing ever invoked itdb:seed:dev/db:seed:usersand the per-domain dev seed files, but stopped short of wiring setup to call themHow did you approach the change?
--seed-devflag tobin/setup: when present it runsdb:seed:dev(which chains the basedb:seedfirst); otherwise it stays on plaindb:seedso CI and lean setups are unaffected--seed-devfrombin/conductor-setup, since Conductor workspaces are always devnpm cifrombin/conductor-setup(bin/setupalready runs it) and clarified the surrounding commentAnything else to add?
bin/rails db:seed:devonce to populate, or re-run setupdb:seed:devis dev-only by design; the defaultdb:seedpath is preserved for production-style and CI runs