Use `bin/rails` rather than `rake` for deployment tasks
Open
- Dominant language
- Ruby
- Stars
- 901
- Forks
- 262
- PR merge metrics
- No merged PRs in 30d
Description
Because this is the documented way of running migrations https://guides.rubyonrails.org/active_record_migrations.html#running-migrations
and this runs the migrations in the current bundle context if they are using bundler, without any extra capistrano gems required.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the deployment tasks that invoke `rake` and compare them with the Rails migration documentation linked in the issue. Confirm the expected command in the current Bundler context, then verify that the deployment tasks use `bin/rails` and still run migrations correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rails, ruby
- Domain
- devops
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100