Laravel的調(diào)度任務(wù)通過內(nèi)置調(diào)度器簡化了任務(wù)管理。首先在App\Console\Kernel類的schedule()方法中定義任務(wù)，例如運(yùn)行Artisan命令、執(zhí)行閉包或調(diào)用腳本；其次使用頻率快捷方法如->daily()、->hourly()等設(shè)置執(zhí)行週期；接著可通過環(huán)境過濾->environments()、條件判斷->when()等控制任務(wù)運(yùn)行條件；最後通過手動執(zhí)行php artisan schedule:run測試任務(wù)，並結(jié)合日誌和監(jiān)控工具確保任務(wù)正常運(yùn)行。

Scheduling tasks in Laravel is straightforward thanks to its built-in task scheduler. You don't need to manually set up multiple Cron entries — just define your schedule inside the App\Console\Kernel class, and Laravel handles the rest.

Define Commands in the Kernel

The main place you'll work with scheduling is the schedule() method in app/Console/Kernel.php . This is where you define all your scheduled tasks.

Common examples include running an Artisan command daily, executing a Closure at specific intervals, or even calling a shell script.

Here's how you might schedule a daily command:

 protected function schedule(Schedule $schedule)
{
    $schedule->command('emails:send-daily')->daily();
}

You can also run closures:

 $schedule->call(function () {
    DB::table('visits')->deleteOldRecords();
})->daily();

Make sure your server has a single Cron entry pointing to Laravel's scheduler:

 * * * * * php /path-to-your-project/artisan schedule:run >> /dev/null 2>&1

Use Common Scheduling Frequencies

Laravel gives you many frequency shortcuts so you don't have to remember Cron syntax. Here are some of the most useful ones:

• ->everyMinute() – Runs every minute
• ->hourly() – Once per hour
• ->daily() – Midnight every day
• ->weekly() – Every Sunday at midnight
• ->monthly() – First day of the month at midnight
• ->weekdays() – Monday through Friday
• ->sundays() , ->mondays() , etc. – Specific days
• ->dailyAt('10:30') – At a specific time every day

For example, if you want to clear cache every hour:

 $schedule->command('cache:clear')->hourly();

Or send reports every Monday morning:

 $schedule->command('reports:send-weekly')->mondays()->at('08:00');

These shortcuts make it much easier to read and write schedules without dealing with raw Cron expressions.

Add Conditions and Filters

Sometimes you may only want a task to run under certain conditions. Laravel provides several ways to control when a scheduled task should actually execute.

Some useful filters include:

• ->environments(['production']) – Only run on specific environments
• ->when(Closure) – Run only if the closure returns true
• ->skip(Closure) – Skip if closure returns true

Example:

 $schedule->command('backup:database')
         ->daily()
         ->environments(['production'])
         ->when(function () {
             return config('services.backups.enabled', false);
         });

This ensures backups only run in production and only if they're enabled in config.

Also, you can chain methods for more fine-grained control, like sending notifications only when something goes wrong using onFailure() or logging output via storeOutputIn() .

Test and Monitor Scheduled Tasks

It's easy to forget that scheduled tasks aren't visible unless they fail or produce output. So testing them matters.

To test a scheduled command manually, run:

 php artisan schedule:run

This checks all defined tasks and runs any that are due.

If you want to log output for debugging or monitoring:

 $schedule->command('data:sync')
         ->hourly()
         ->storeOutputIn(storage_path('logs/scheduler.log'))
         ->appendOutputTo(storage_path('logs/scheduler.log'));

Monitoring tools like Laravel Horizon or third-party services (eg, Oh Dear, Clockwork) can help track missed or failed jobs.

Also, be aware that overlapping tasks can cause issues. Use ->withoutOverlapping() to prevent multiple instances of the same task from running at once.

That's basically it. Laravel's scheduler covers most use cases without getting too complex — as long as you remember to set up the Cron entry and test your tasks occasionally.

以上是如何使用Laravel調(diào)度程序安排任務(wù)？的詳細(xì)內(nèi)容。更多資訊請關(guān)注PHP中文網(wǎng)其他相關(guān)文章！