scheduled stuff can be a pain unless you get them right. remember those times when an invoice wasn't sent out or reports ran into issues? that's exactly what happened, and suddenly scheduled work isn't just "server nonsense" but smth crucial for your product's success.
for years i relied on adding lines to crontab files as if it was a one-size-fits-all solution. big mistake! tasks got scattered outside the codebase making them hard to manage later down the line ⚡
now, w/ laravel scheduler in use at my projects (and yes - this is what you should be using too), i've found that setting up and managing scheduled jobs within your app itself makes so much more sense. it's all right there where everything else lives.
so here's how: first off,
$schedule->command('your-command')->daily(); // or whatever schedule works for ya!
then, just make sure to run `cron artisan scheduler` on a regular basis (i set mine up with an hourly cron job) ⬆
what do you guys think? have any other tips that work well in production?
more here:
https://dev.to/blamsa0mine/laravel-scheduler-in-production-why-i-use-it-and-how-i-make-it-reliable-43df