-
Notifications
You must be signed in to change notification settings - Fork 725
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
Whenever 0.9.4 generating runner commands with script/runner, which does not exist in Rails 4 #588
Comments
I worked around this by adding a custom runner to the
but I am still wondering why would whenever generate the deprecated script/runner command on a rails 4 project? |
Yeah, I had the same problem, I assume you are running that command on your server, inside your current production directory. And you are using Capistrano 3 for deployment. In that case, go to your For some reason, capistrano 3 contributors decided to share the remove |
Also I have found that after each deployment, you need to first edit your crontab and remove the entry for the previous release and then run |
Awesome! Thanks @alitivay !! Now my emails work perfectly. PD: just with removing the
|
Excellent ! |
I didn't know why my cronjob wasn't work... But thank you guys, i was scared hahah... Thank you for the great helo. 👍 |
@alitivay You're a champ 🥳 |
I am using rails 4.2.3 with whenever 0.9.4 and capistrano 3.1. Everything related to scheduling cron jobs works fine except that I get periodic errors in my cron.log (in production) with the following content:
then in my crontab -l I have the following:
which curiously uses the "script/runner" command, which is no longer available in Rails 4 according to this topic on stackoverflow:
http://stackoverflow.com/questions/19683405/why-is-rails-runner-e-production-not-working
furthermore, I have included the
require 'capistrano/bundler'
in my Capfile, and I expect the generated the cron command to contain something like this:instead of
currently I am thinking about creating a custom job_type that manually generates the required rails runner command, but I think this is an issue worth resolving.
The text was updated successfully, but these errors were encountered: