Skip to content

Update guidance on development environment seed data. #721

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion rails/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@
- Validate the associated `belongs_to` object (`user`), not the database column
(`user_id`).
- Use `db/seeds.rb` for data that is required in all environments.
- Use `dev:prime` rake task for development environment seed data.
- Use `development:seed` rake task for development environment seed data.
Copy link
Contributor

Choose a reason for hiding this comment

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

idea (non-blocking): What would you think about using development:db:seed?

  • This would mirror the db:seed rake task, but append the environment context to the front.
  • would leave room for things like development:redis:seed

note - mentioned this in slack already, adding here for posterity

- Prefer `cookies.signed` over `cookies` to [prevent tampering].
- Prefer `Time.current` over `Time.now`
- Prefer `Date.current` over `Date.today`
Expand Down