Crons & Supervisors Reference

Use cron:* commands to manage scheduled jobs and supervisor:* commands to define and operate long-running site processes.

At a Glance

Cron Commands

Supervisor Commands

Inventory vs Remote Sync

Both crons and supervisors follow the same two-phase pattern: create and delete update local inventory state, while sync is the command that applies those definitions to the server. This split lets you stage changes safely before pushing them to production.

Your site must have at least one successful deployment before you can create crons or supervisors, because scripts are validated against the deployed repository.

Cron Details

Creating a Cron Job

cron:create prompts you for a script path and a cron schedule expression. Before saving, it validates that:

• The script exists in the site's remote Git repository
• No duplicate cron with the same script is already configured for the site
• The schedule expression is a valid five-field cron format (minute, hour, day, month, weekday), including support for wildcards, ranges, lists, steps, and month/weekday name aliases

After creation, run cron:sync to apply the definition to the server.

Deleting a Cron Job

cron:delete requires you to type the cron identifier to confirm deletion. After removing the definition from inventory, run cron:sync to update the server.

Supervisor Details

Creating a Supervisor Program

supervisor:create prompts you for a script path and a program name, then collects configuration parameters:

• Autostart controls whether the program starts when supervisord starts (default: yes)
• Autorestart controls whether the program restarts on exit (default: yes)
• Stop wait seconds sets how long to wait for a graceful stop (default: 3600)
• Number of processes sets how many instances to run (default: 1)

Before saving, it validates that the script exists in the site's remote Git repository and that neither the script path nor the program name is already configured for the site.

After creation, run supervisor:sync to apply the definition to the server.

Deleting a Supervisor Program

supervisor:delete requires you to type the program identifier to confirm deletion. After removing the definition from inventory, run supervisor:sync to update the server.

Lifecycle Control

Use supervisor:start, supervisor:stop, and supervisor:restart for daemon lifecycle control. These operate on the supervisord service itself, which manages all configured programs on the server.