Manage your Laravel Schedule from a pretty dashboard. Schedule your Laravel Console Commands to your liking. Enable/Disable scheduled tasks on the fly without going back to your code again.

• PHP 8.3+
• Laravel 12.x or 13.x

Earlier Totem majors are maintained for legacy Laravel support:

• Totem 12.x supports Laravel 11.x and 12.x (PHP 8.2+).
• Totem 11.x supports Laravel 10.x, 11.x, and 12.x (PHP 8.2+).

Use composer to install Totem into your Laravel project:

composer require studio/laravel-totem

Once Laravel Totem is installed, run the migration and publish the assets:

php artisan migrate
php artisan totem:assets

Republish Totem assets after updating to a new version:

php artisan totem:assets

This package assumes that you have a good understanding of Laravel's Task Scheduling and Laravel Console Commands. Before any of this works please make sure you have a cron running as follows:

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

Laravel Totem's dashboard is inspired by Laravel Horizon. Just like Horizon you can configure authentication to Totem's dashboard. Add the following to the boot method of your AppServiceProvider:

use Studio\Totem\Totem;

Totem::auth(function($request) {
    // return true / false . For e.g.
    return Auth::check();
});

By default Totem's dashboard only works in the local environment. To view the dashboard point your browser to /totem of your app.

Totem's tables use generic names which may conflict with existing tables in a project. To alleviate this the .env param TOTEM_TABLE_PREFIX can be set which will apply a prefix to all of Totem's tables and their models.

By default Totem uses your application's default cache store. In environments where UI servers and background worker servers use separate cache clusters (e.g. different Redis instances), Totem's cache can become inconsistent — a bust event on one server won't clear the cache on the other.

Set TOTEM_CACHE_STORE to a named store from your config/cache.php that is accessible by all servers:

TOTEM_CACHE_STORE=redis-shared

Setting it to array disables cache persistence entirely (each request hits the database):

TOTEM_CACHE_STORE=array

Leaving it unset uses your application's default cache store (existing behaviour).

By default Totem outputs all Artisan commands on the Create/Edit tasks. To make this dropdown more concise there is a filter config feature that can be set in the totem.php config file.

Example filters:

'artisan' => [
    'command_filter' => [
        'stats:*',
        'email:daily-reports'
    ],
],

This feature uses fnmatch syntax to filter displayed commands. stats:* will match all Artisan commands that start with stats: while email:daily-reports will only match the command named email:daily-reports.

This filter can be used as either a whitelist or a blacklist. By default it acts as a whitelist but an option flag can be set to instead act as a blacklist:

'artisan' => [
    'command_filter' => [
        'stats:*',
        'email:daily-reports'
    ],
    'whitelist' => false,
],

Laravel Totem uses the web middleware by default. If customization is required the middleware can be changed by setting the TOTEM_WEB_MIDDLEWARE value in your .env. These values can be found in config/totem.php.

Totem can send notifications when a task completes. Email notifications are included out of the box. For SMS (Vonage) or Slack notifications, install the relevant package:

composer require laravel/vonage-notification-channel
composer require laravel/slack-notification-channel

All artisan commands are available for scheduling. If you want to hide a command from Totem set the hidden attribute to true in your command:

protected $hidden = true;

If your command requires arguments or options use the optional command parameters field. You can provide parameters as a string in the following format:

name=john.doe --greetings='Welcome to the new world'

In the example above, name is an argument while greetings is an option.

Totem provides an artisan command to view a list of scheduled tasks:

php artisan schedule:list

You can pause the scheduled runs of every task at once, for example during an incident or a deploy. Each task keeps its own enabled/disabled setting, so resuming puts everything back exactly as it was. Running a task manually with the Execute button still works while tasks are paused.

From the dashboard, use Pause All at the bottom of the task list. You can pause until you resume manually, for a preset length of time, or until a specific date and time. While tasks are paused, the task list shows a notice with a Resume button.

The same is available from the command line:

php artisan totem:pause                              # until resumed
php artisan totem:pause --until="2026-10-08 09:00"   # resume automatically at that time
php artisan totem:resume

Resume times entered on the dashboard are in the app timezone (config('app.timezone')), which is shown next to the field. --until also uses the app timezone unless you include one, for example --until="2026-10-08 09:00 America/New_York".

A pause with a resume time ends on its own when that time passes; no additional job is required. The pause is stored in the schedule_pauses table, so run php artisan migrate after updating.

Important versions listed below. Refer to the Changelog for a full history of the project.

• Roshan Gautam
• OSS Contributors

Bug reports, feature requests, and pull requests can be submitted by following our Contribution Guide.

• Versioning
• Coding Standards
• Pull Requests

This software is released under the MIT License.

© 2025 Roshan Gautam, All rights reserved.