a month ago
Say you’ve got 10 different cron jobs you want to run.
From what I understand, you’d need to create a separate service for each one and configure its schedule individually.
Am I missing something here, or is that actually how it’s meant to work? It seems like it would be pretty hard to manage.
Currently I have set up one cron job to run every hour, and in my service I do date lookups to see which cron/service function I should trigger. Which is also not great.
Thanks!
4 Replies
a month ago
Yeah, 10 different jobs is 10 services. That's a lot of jobs. Have you considered using a larger script to manage multiple of these jobs? Then you could run them all in one container.
samgordon
Yeah, 10 different jobs is 10 services. That's a lot of jobs. Have you considered using a larger script to manage multiple of these jobs? Then you could run them all in one container.
a month ago
Have you considered using a larger script to manage multiple of these jobs?
This sounds like what I tried to explain here:
Currently I have set up one cron job to run every hour, and in my service I do date lookups to see which cron/service function I should trigger. Which is also not great.
Or did you mean something else?
a month ago
Well- you could set up a script that runs multiple cron jobs instead of just one.
samgordon
Well- you could set up a script that runs multiple cron jobs instead of just one.
a month ago
I'm not sure I follow - how would you do that (assuming this is different/better than just creating multiple cron services in the web UI) ?
Also, is it just me or would it make absolute sense to support configuring multiple cron tasks here (instead of just one):
Attachments