Планировщик задач
In the past, you may have generated a Cron entry for each task you needed to schedule on your server. However, this can quickly become a pain, because your task schedule is no longer in source control and you must SSH into your server to add additional Cron entries.
Laravel's command scheduler allows you to fluently and expressively define your command schedule within Laravel itself. When using the scheduler, only a single Cron entry is needed on your server. Your task schedule is defined in the app/Console/Kernel.php
file's schedule
method. To help you get started, a simple example is defined within the method.
Starting The Scheduler
When using the scheduler, you only need to add the following Cron entry to your server. If you do not know how to add Cron entries to your server, consider using a service such as Laravel Forge which can manage the Cron entries for you:
This Cron will call the Laravel command scheduler every minute. When the schedule:run
command is executed, Laravel will evaluate your scheduled tasks and runs the tasks that are due.
You may define all of your scheduled tasks in the schedule
method of the App\Console\Kernel
class. To get started, let's look at an example of scheduling a task. In this example, we will schedule a Closure
to be called every day at midnight. Within the Closure
we will execute a database query to clear a table:
In addition to scheduling using Closures, you may also use invokable objects. Invokable objects are simple PHP classes that contain an __invoke
method:
In addition to scheduling Closure calls, you may also schedule Artisan commands and operating system commands. For example, you may use the command
method to schedule an Artisan command using either the command's name or class:
The job
method may be used to schedule a queued job. This method provides a convenient way to schedule jobs without using the call
method to manually create Closures to queue the job:
The exec
method may be used to issue a command to the operating system:
There are a variety of schedules you may assign to your task:
These methods may be combined with additional constraints to create even more finely tuned schedules that only run on certain days of the week. For example, to schedule a command to run weekly on Monday:
Below is a list of the additional schedule constraints:
Day Constraints
The days
method may be used to limit the execution of a task to specific days of the week. For example, you may schedule a command to run hourly on Sundays and Wednesdays:
Between Time Constraints
The between
method may be used to limit the execution of a task based on the time of day:
Similarly, the unlessBetween
method can be used to exclude the execution of a task for a period of time:
Truth Test Constraints
The when
method may be used to limit the execution of a task based on the result of a given truth test. In other words, if the given Closure
returns true
, the task will execute as long as no other constraining conditions prevent the task from running:
The skip
method may be seen as the inverse of when
. If the skip
method returns true
, the scheduled task will not be executed:
When using chained when
methods, the scheduled command will only execute if all when
conditions return true
.
Environment Constraints
The environments
method may be used to execute tasks only on the given environments:
Using the timezone
method, you may specify that a scheduled task's time should be interpreted within a given timezone:
If you are assigning the same timezone to all of your scheduled tasks, you may wish to define a scheduleTimezone
method in your app/Console/Kernel.php
file. This method should return the default timezone that should be assigned to all scheduled tasks:
Remember that some timezones utilize daylight savings time. When daylight saving time changes occur, your scheduled task may run twice or even not run at all. For this reason, we recommend avoiding timezone scheduling when possible.
By default, scheduled tasks will be run even if the previous instance of the task is still running. To prevent this, you may use the withoutOverlapping
method:
In this example, the emails:send
Artisan command will be run every minute if it is not already running. The withoutOverlapping
method is especially useful if you have tasks that vary drastically in their execution time, preventing you from predicting exactly how long a given task will take.
If needed, you may specify how many minutes must pass before the "without overlapping" lock expires. By default, the lock will expire after 24 hours:
To utilize this feature, your application must be using the
database
,memcached
, orredis
cache driver as your application's default cache driver. In addition, all servers must be communicating with the same central cache server.
If your application is running on multiple servers, you may limit a scheduled job to only execute on a single server. For instance, assume you have a scheduled task that generates a new report every Friday night. If the task scheduler is running on three worker servers, the scheduled task will run on all three servers and generate the report three times. Not good!
To indicate that the task should run on only one server, use the onOneServer
method when defining the scheduled task. The first server to obtain the task will secure an atomic lock on the job to prevent other servers from running the same task at the same time:
By default, multiple commands scheduled at the same time will execute sequentially. If you have long-running commands, this may cause subsequent commands to start much later than anticipated. If you would like to run commands in the background so that they may all run simultaneously, you may use the runInBackground
method:
The
runInBackground
method may only be used when scheduling tasks via thecommand
andexec
methods.
Laravel's scheduled tasks will not run when Laravel is in maintenance mode, since we don't want your tasks to interfere with any unfinished maintenance you may be performing on your server. However, if you would like to force a task to run even in maintenance mode, you may use the evenInMaintenanceMode
method:
The Laravel scheduler provides several convenient methods for working with the output generated by scheduled tasks. First, using the sendOutputTo
method, you may send the output to a file for later inspection:
If you would like to append the output to a given file, you may use the appendOutputTo
method:
Using the emailOutputTo
method, you may e-mail the output to an e-mail address of your choice. Before e-mailing the output of a task, you should configure Laravel's e-mail services:
If you only want to e-mail the output if the command fails, use the emailOutputOnFailure
method:
The
emailOutputTo
,emailOutputOnFailure
,sendOutputTo
, andappendOutputTo
methods are exclusive to thecommand
andexec
methods.
Using the before
and after
methods, you may specify code to be executed before and after the scheduled task is complete:
The onSuccess
and onFailure
methods allow you to specify code to be executed if the scheduled task succeeds or fails:
Pinging URLs
Using the pingBefore
and thenPing
methods, the scheduler can automatically ping a given URL before or after a task is complete. This method is useful for notifying an external service, such as Laravel Envoyer, that your scheduled task is commencing or has finished execution:
The pingBeforeIf
and thenPingIf
methods may be used to ping a given URL only if the given condition is true
:
The pingOnSuccess
and pingOnFailure
methods may be used to ping a given URL only if the task succeeds or fails:
All of the ping methods require the Guzzle HTTP library. You can add Guzzle to your project using the Composer package manager:
Last updated