laravel has a scheduler https://laravel.com/docs/5.3/scheduling
you can run a scheduler task to accomplish what you need.
Yeah, I know about that. But somehow jobs feel cleaner to use in this case, especially for the reason, that these tasks should only run once, at a given time, not on a schedule. Is my solution any worse than using the scheduler?
yep, my idea is to run a cron: take all the events matching the date range, dispatch jobs/job to process them. the jobs will run in the background and exit when done.
rmugunda liked this reply
Sign in to participate in this thread!
Laravel
Laravel News
Laracasts
Laravel Podcast