- How do I install shuvroroy/filament-spatie-laravel-backup in a Laravel app?
- Install it with Composer using composer require shuvroroy/filament-spatie-laravel-backup. Then publish the package assets with php artisan filament:assets. Optionally publish the translations with php artisan vendor:publish --tag=filament-spatie-backup-translations. Finally register FilamentSpatieLaravelBackupPlugin::make() in your panel provider.
- Does this package work with Filament v3 and v4?
- The package tracks Filament majors and its plugin registration plus typed navigation property imply Filament v3.2+ or v4. Because it follows Filament releases, you should pin a compatible package version for your Filament major. Check the release metadata and the 1.x to 2.0 upgrade guide before upgrading Filament. Plan plugin upgrades in lockstep with major Filament bumps.
- How do I register FilamentSpatieLaravelBackupPlugin in my panel provider?
- Add use ShuvroRoy\FilamentSpatieLaravelBackup\FilamentSpatieLaravelBackupPlugin at the top of your PanelProvider. Inside the panel method, chain ->plugin(FilamentSpatieLaravelBackupPlugin::make()) on the Panel instance. After that, a Backups page appears in the Filament admin navigation. No custom page or table code is required.
- How do I customize the Backups page icon, heading, or navigation?
- You can extend ShuvroRoy\FilamentSpatieLaravelBackup\Pages\Backups and override properties such as navigationIcon or methods such as getHeading. Then register your custom page with the plugin using the documented usingPage() path. The plugin also exposes fluent options for navigation icon, label, group, and sort order, including closure support. This lets you move the page under Settings or Core without forking the package.
- How do I control who can create, download, or delete backups?
- Authorization is opt-in. The authorize() method gates access to the Backups page, but the create-backup, download-backup, and delete-backup permissions must be seeded and assigned by you. Map those permissions to a named backup role rather than individual users. Do not assume least privilege works out of the box. If downloading is not required, de-scope that permission entirely.
- Does this package replace spatie/laravel-backup or require it?
- It does not replace spatie/laravel-backup; it is a thin Filament presentation layer on top of it. The package reads and drives your existing config/backup.php configuration, disks, and queued backup jobs. Your Spatie backup policy remains the system of record. This means no new persistence model, no schema changes, and no parallel backup pipeline.
- How are backups queued and what happens if the queue worker is down?
- Backup creation is driven by spatie/laravel-backup jobs, so your configured queue connection and worker pool execute the work. The plugin provides usingQueue() to choose the queue, plus timeout() and noTimeout() controls for job execution. If the worker is down, the backup job will not complete and the UI state may not reflect a finished archive. Monitor your queue workers independently of this UI.
- Can I disable or remove the backup download feature?
- Yes, download is controlled by the download-backup permission, so you can simply avoid granting it to any role. Downloading streams archives through the browser and PHP-FPM or web workers to an admin laptop, which is the highest-risk data-handling feature. If your process requires restores through a controlled runbook, de-scope downloads and keep restore operations out of the admin UI. This reduces exposure of database dumps.
- How do I publish translations and other assets for this Filament backup page?
- Run php artisan filament:assets to publish the package assets required by Filament. To localize the interface, publish translations with php artisan vendor:publish --tag=filament-spatie-backup-translations. The published language files can then be customized for your admin panel. No frontend build changes are needed beyond publishing assets.
- What are the main maintenance risks or alternatives to this package?
- The dominant risk is version coupling: every Filament major bump becomes a plugin upgrade you must schedule. It is also a single-maintainer package with thin adoption, though the MIT license and small surface area mean you can vendor or fork a few hundred lines if needed. The load-bearing backup engine is Spatie's mature package. Alternatives include using spatie/laravel-backup artisan commands directly, building a small custom Filament page, or relying on managed database snapshots and cloud provider tooling.