rufus-scheduler is not a replacement for cron
can be expanded before "rufus-scheduler has never been written as a replacement for cron". The big message is "you are a developer, and as a developer you should know the environment that you inherit and the tools that it comes with. You need to know when to use them, when to simulate them, when to replace them."
Rufus-scheduler understands the syntax of "* * * * *" Cron. This made some people say, "rufus-scheduler is trying to replace Cron." It could be formulated as follows: "Some people abuse the rufus-planner instead of thinking (knowing) that the old faithful Kron would be better in this situation."
To become a good developer, you should seriously think about some sixadmin * nix skills, otherwise it will hurt to work. It can be as simple as "installing, starting, and managing a Linux box in VirtualBox on your system."
The rufus-scheduler schedule runs in the Ruby process. In the vanilla world, the rufus scheduler runs in the same Ruby process that serves HTTP requests (a Rails or Sinatra web application), and, oh, oops, schedules do not start when the application does not start.
Cron is a service provided by your * nix operating system. Other applications and services on your host rely on it. Cron reads its crontab and runs the script specified in it at the specified times. Thanks to a great time when Cron can run scripts in a Rails application.
This may interest you: https://devcenter.heroku.com/articles/clock-processes-ruby
source share