We've always used Window's Task Scheduler for our CRON jobs.
Let the app not have to worry about it being a scheduled task, and let Windows worry about that instead.
Deployment configuration creates the scheduled task and determines time of day / enabled status.
This seems like an interesting alternative, and allows more control at the application level. But comparatively in our current configuration, to change the time of day or enabled/disabled status, we don't have to deploy a new version of the application to PROD, just change it in the task scheduler.
The Pro dashboard seems a lot more user friendly way of dealing with the tasks too, and wouldn't require as many user permissions.
One of the issues it seems many devs run into with Window's task scheduler are, as you said, basic user permissions 😂.
Plus, if you want to move all your infrastructure to serverless / container services, etc. then with something like Coravel you literally have nothing to change. Using Windows Task Scheduler def. couples you to using a full VM or bare-metal infra.
And yes, Coravel Pro stores all the schedules in your DB so you can just change schedules on PROD with no deployments 👍
.NET Core 3 will have lots of cool stuff! Looking forward to it.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Interesting!
We've always used Window's Task Scheduler for our CRON jobs.
This seems like an interesting alternative, and allows more control at the application level. But comparatively in our current configuration, to change the time of day or enabled/disabled status, we don't have to deploy a new version of the application to PROD, just change it in the task scheduler.
The Pro dashboard seems a lot more user friendly way of dealing with the tasks too, and wouldn't require as many user permissions.
Thanks for the tutorial
Thanks for the feedback!
One of the issues it seems many devs run into with Window's task scheduler are, as you said, basic user permissions 😂.
Plus, if you want to move all your infrastructure to serverless / container services, etc. then with something like Coravel you literally have nothing to change. Using Windows Task Scheduler def. couples you to using a full VM or bare-metal infra.
And yes, Coravel Pro stores all the schedules in your DB so you can just change schedules on PROD with no deployments 👍
.NET Core 3 will have lots of cool stuff! Looking forward to it.