Cedar8mo ago

Any tutorial links to help me understand the Schedule string in Deno.cron()

I am currently working on an issue on the deno repo and I am trying to reconstruct the deno schedule string from an object, but I am finding it a little bit hard to find any resources that explains the Deno.cron() function parameters especially the schedule string. I would really appreaciate it if anyone could help explain the schedule string or at least provide some resources I could read it up on. I got this image from the issue but the thing is that most of the asterix doesn't make sense at least to me. I understand there is minute, hour and days_of_week but there are two unidentified * that I don't really know what they reperesent.
No description
4 Replies
Deno AI Helper
Deno AI Helper8mo ago
I'm sorry, but based on the documentation provided, there is no mention of a Deno.cron() function or any related scheduling or cron functionality within Deno. It's possible that you might be referring to a third-party library or module that isn't covered in the official Deno documentation. If you're working with a specific library or module, I would recommend checking the documentation or README associated with that library. If you're still having trouble, you might find it helpful to ask for clarification in the Deno community on Discord or Stack Overflow, as mentioned in the Deno manual's Help section. 🦕
raunioroo8mo ago
the format is based on a linux/unix program "cron", so there are lot of resources available if you search for the cron program docs and manuals. https://crontab.guru/ is pretty nice. also any number of online tutorials, just a random one that looks decent https://www.baeldung.com/cron-expressions
EthanThatOneKid8mo ago
Add JS-friendly API for specifying Deno.cron schedule · Issue #2112...
Currently Deno.cron() 2nd argument is a string, which specifies the schedule using the cron format. We'd like to extend this with a JS-friendly API, which allows the schedule to be specified us...
Cedar8mo ago
Thanks just found out its was the same as the Unix cron schedule string