Configuration.

Publishing config/checklist.php is optional. Publish it before migrating when you need different table names, or later when the storage, schedule, or notification defaults do not fit your application.

php artisan vendor:publish --tag="checklist-config"

Table names

Every key must exist and contain a non-blank string. The service provider validates the map during boot. Package models and migrations resolve names through the same map.

Changing a value after migration does not rename an existing table.

Section depth

'max_section_depth' => 3,

A top-level section has depth one. The builder checks depth while authoring, and publication checks the persisted tree again. Integer values and unsigned numeric strings are accepted. Invalid values fall back to three.

Evidence disk

'evidence' => [
    'disk' => env('CHECKLIST_EVIDENCE_DISK', 'local'),
],

The value must name a Laravel filesystem disk. A missing or blank runtime value falls back to local.

The package writes and deletes on this disk. It does not configure visibility or generate URLs.

Due-soon lead time

'due_soon_lead_time' => env(
    'CHECKLIST_DUE_SOON_LEAD_TIME',
    24 * 60,
),

The value is minutes before due_at. Non-negative integers and digit-only strings are accepted. Negative integers become zero. Other values fall back to 1,440 minutes.

The transition fires once per open checklist when checklist:generate-due runs inside this window.

Notification settings

'notifications' => [
    'enabled' => env('CHECKLIST_NOTIFICATIONS', true),
    'recipient_resolver' =>
        ByRcsc\LaravelChecklist\Notifications\DefaultRecipientResolver::class,
    'classes' => [],
],

enabled disables only shipped notification delivery when its value is the boolean false.

recipient_resolver must name a class implementing Contracts\RecipientResolver. The dispatcher resolves that class from the container.

classes maps an event class to a Laravel notification class or null. A missing event key uses the shipped default. A null value silences that event.

Published assets

Publish configuration before migrations when table names differ from the defaults. Translation publication is optional.

What to read next

• Installation and setup for the required publication order.
• Customize notifications for resolver and class examples.
• Troubleshooting for boot-time configuration failures.