Whenever doesn’t detect your environment, it just defaults to using production. You can set the environment for all jobs using set: set :environment, ‘staging’ Or per job: every 2.hours do runner ‘My.runner’, :environment => ‘staging’ end
Clear existing cron jobs. crontab -r Update cronjob with the environment. whenever –update-crontab –set environment=”development”
Short answer: use the scheduler add-on: http://addons.heroku.com/scheduler Long answer: When you do heroku run, we spin up a dyno put your code on it execute your command, wait for it to finish throw the dyno away Any changes you made to crontab would be immediately thrown away. Everything is ephemeral, you cannot edit files on … Read more
Short answer is they are the same thing. ActiveJob calls it a Job whereas Sidekiq calls it a Worker. I’ve decided to keep the terminology different so that people can distinguish the two. You can use either one. Note that ActiveJob does not provide access to the full set of Sidekiq options so if you … Read more
You can also ensure your PATH ends up in the crontab, by putting the following at the top of the schedule.rb file: env :PATH, ENV[‘PATH’] https://groups.google.com/forum/#!msg/whenever-gem/yRLt3f2jrfU/Exu3xfCo8DAJ If above solution don’t work for you, try: env :GEM_PATH, ENV[‘GEM_PATH’]