Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
@reboot nickname support
See original GitHub issueFirst of all thanks for this great utility! I’m currently implementing a scheduling for BetonQuest using a cron syntax (-> BetonQuest/BetonQuest#1885) and it saves a ton of work.
Only thing I’m still missing but really would love to implement is support to run stuff on startup using the @reboot nickname just like it’s known from the crontab syntax.
So I wonder what would be the best way to implement it. Is there any way I can create a CronDefinition that allows @reboot or even add/check for custom nicknames?
If not is there anything like that planned or is this out of scope?
If this doesn’t work out with cron-utils I have to implement that check separately but I would always prefer a native solution.
Issue Analytics
- State:
- Created a year ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@J0B10 thank you for the comments! 😄 We thought about nicknames as enums, given there are just a few keywords used across the multiple cron definitions and implementations. Therefore, it makes sense to restrict the nicknames to those options. We will check, and come back with a tentative implementation. Regarding the cron translation, if no conversion is possible, then we could throw an exception. Not all crons are “convertible” 😄 Thanks again!
@J0B10 thanks! 🚀 😎