cap development whenever:update_crontab silently succeeds, does nothing
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 8.9k
- Forks
- 715
- PR merge metrics
- No merged PRs in 30d
Description
When I run cap development whenever:update_crontab, it appears to silently succeed, with no output, and the crontab on the server is not updated. Likewise, cap development deploy shows no whenever-related activity.
In my Capfile:
require 'whenever/capistrano'
In deploy/development.rb:
In my deploy.rb:
set :whenever_identifier, -> { "#{fetch(:application)}_#{fetch(:stage)}" }
set :whenever_environment, -> { fetch(:stage, 'production') }
My schedule.rb:
set :output, 'logs/dash2-harvester.log'
every 15.minutes do
command "STASH_ENV=#{@environment} /apps/dash2/apps/dash2-harvester/bin/harvest.sh"
end
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce cap development whenever:update_crontab and cap development deploy, then inspect Capfile, deploy/development.rb, deploy.rb, and schedule.rb alongside the required Whenever integration. Done means the update command reports activity and the server crontab reflects the scheduled harvest command, with deployment showing the related activity.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- cli, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100