8 commits

Author	SHA1	Message	Date
mfo	08ec45443d	BREAKING(sidekiq.queues): rationalize queues. now have critical, default, low ... Dear instances, make sure to update your sidekiq processes. Indead, we are adopting a new strategy for daemons that process our background jobs. Now their is only 3 queues on sidekiq (still, we keep archive/export on delayed job for now). The big idea : allow any worker to deal with any queue (capacity mgmt) : - critical: must be procesed now - default: will be processed asap - low: do it after everything else FYI: we had 50% of our server capacity on reserved queues. Leading to bottle neck processing (reserved queues/worker not processing other queues). We HAD TO fix it. Sorry for the inconvenience TBH, this is an idea of Colin Darie <colin@darie.eu>. I'm just pushing it forward. Co-Authored-By: Colin Darie <colin@darie.eu>	2024-09-24 21:29:11 +02:00
Colin Darie	77fb0553fc	chore: enable freeze string literals by comment	2024-08-22 09:26:48 +02:00
Colin Darie	dfbe53dcc5	fix(cron): really schedule jobs on sidekiq instead of running them	2024-04-10 18:03:47 +02:00
Colin Darie	25892f594c	fix(jobs): don't enqueue crons to default adapter anymore	2024-04-08 18:27:31 +02:00
simon lehericey	42af5a9149	make cron_job work with both delayed_job and sidekiq	2024-04-04 16:38:38 +02:00
simon lehericey	016c392914	tech: add env var to disable cron scheduling	2023-12-14 17:12:19 +01:00
Christophe Robillard	0e3e6eb62a	add schedulable? class method to cron jobs	2022-07-21 21:54:15 +02:00
clemkeirua	513d4f6ff1	move all the cron jobs in a dedicated directory	2020-12-08 13:22:43 +00:00

Renamed from app/jobs/cron_job.rb (Browse further)