Sidekiq-Cron VS Whenever

sidekiq-cron

this might be useful? https://github.com/ondrejbartas/sidekiq-cron

Depending on how far into the future you're planning to, it could be worth storing the datetime you want it executed on a field like perform_work_at within your database. Then use sidekiq-cron to check a few times a day for if the perform_work_at has passed & the work needs to be done.

The cron job itself was not a huge hassle; the sidekiq-cron gem worked really well for me here to get everything configured in the application.

If what you need is a job (related to application) you can use sidekiq with sidekiq-cron [https://github.com/ondrejbartas/sidekiq-cron] running every x seconds or when a job ends starts a new one.

Learn about Unix cron and use the whenever gem.

there are cronjob gems available, i believe https://github.com/javan/whenever or so seems to be used frequently

- Use them on a specific schedule as needed by your application, such as taking backups, sending periodic reminders or notifications for users, cleaning the database tables, etc. You can use a gem such as Whenever for managing scheduled cron jobs.

whenever gem is used in Rails applications to schedule cron jobs e.g. send email notification about monthly expenditure on the 1st of each month.

Then you can use the whenever gem to schedule stuff.

- [whenever](https://github.com/javan/whenever)

whenever

There are multiple ways to achieve this. Probably the simplest and most reliable is to rely on cron to run your process every minute. Cron keeps track of time and executes your script each minute. This has the added benefit of avoiding a long running process (which can have its own issues). You can even have your script install it’s own cron job using the Whenever gem.

Rake tasks can be called from Cron, so we'll use the Whenever Gem to automatically add our job to our Crontab during deployment, and keep our schedule in change control.