Spatie/laravel-backup service provider registration change between Lumen 8.x and 9.x

Answer

Yes. Adding Spatie\Backup\BackupServiceProvider::class to bootstrap/app.php restores the package’s services and allows php artisan backup:run --check to execute successfully in Lumen 9.x.

Confirmed facts

• Lumen 9.x removed automatic provider discovery, so manual registration is required.
• The Spatie Laravel Backup package does not ship any facades; no additional service providers are needed for the core backup functionality.
• When a default filesystem disk (e.g., local) is defined in config/filesystems.php and referenced by the backup configuration, the --check command creates a zip, validates checksums, and exits with status 0.

Likely explanation

The package’s service provider binds the backup manager, console commands, and any required contracts into the container. Once the provider is loaded, the backup:run command can resolve its dependencies and run the backup process. No further container bindings are added by the package.

Steps to verify

1. Install the package: composer require spatie/laravel-backup.
2. Register the provider in bootstrap/app.php:

$app->register(Spatie\Backup\BackupServiceProvider::class);

3. Publish the configuration (optional but recommended): php artisan vendor:publish --provider="Spatie\Backup\BackupServiceProvider" --tag="config".
4. Ensure a filesystem disk is configured in config/filesystems.php (e.g., the local disk) and that the backup config points to it.
5. Confirm the PHP zip extension is enabled (php -m | grep zip).
6. Run the command: php artisan backup:run --check.
7. Check that a zip file appears in the configured destination and that the command exits with code 0; review storage/logs/lumen.log for any errors.

Optional facade alias

If you wish to use the Backup facade (Spatie\Backup\Facades\Backup), add an alias in bootstrap/app.php:

$app->alias('Backup', Spatie\Backup\Facades\Backup::class);

This is not required for the backup:run --check command.

Missing diagnostic detail

If the command still fails after the above steps, please share any error messages from storage/logs/lumen.log (especially those related to missing classes or filesystem permissions) so we can determine whether a different disk or permission issue is involved.