- How do I install and configure jpbgomes/laravel-database-backup?
- Install it with Composer using composer require jpbgomes/laravel-database-backup, then publish and review the package configuration. Set your MySQL connection details, chosen storage destination, and mail recipients there, preferably through environment variables. Check the README for the exact publish command and config keys for your installed version.
- Does this package support Laravel 13?
- Release 1.2.0 declares support for Laravel 13 and Symfony Process 8 while keeping earlier version constraints. The release notes describe this as additive support, so existing Laravel 10, 11, and 12 installs are nominally retained. Treat the Laravel 13 claim as declared rather than proven unless you can confirm the package's CI matrix tests that combination.
- How do I schedule automatic database backups in Laravel?
- The package provides Artisan commands that you can register with Laravel's scheduler at the cadence you need. Add the backup command to routes/console.php or your console kernel and run the scheduler via cron or a platform scheduler. Test one manual run first so you know the command name and expected output for your version.
- Where does laravel-database-backup store the backup files?
- The package supports configurable storage destinations, so the backup location is controlled by its configuration rather than being hard-coded. Review the storage disk and path options and make sure the PHP process can write to that location. If you also enable email delivery, confirm whether the file is retained on disk or only sent.
- Can I email MySQL database backups from Laravel with this package?
- Yes, the package description explicitly includes sending backups via email. Configure Laravel's mail settings plus the package's recipient options, then run a manual backup to verify delivery and attachment behavior. For large databases, check mail size limits or prefer a storage link instead of a direct attachment.
- Does jpbgomes/laravel-database-backup work with PostgreSQL or SQLite?
- The supplied package description scopes it to MySQL database backups, and there is no evidence of PostgreSQL, MariaDB, or SQLite support. Do not assume other engines will work without checking the README or testing a dump and restore. If you need multi-database support, compare it with a broader backup package.
- Is this Laravel backup package safe to use in production?
- Treat it as a process-spawning package: the PHP user must be able to execute the MySQL dump binary, write backups outside the web root, and finish within your timeout limits. In containers, verify PATH, permissions, and subprocess behavior rather than assuming a local shell setup. Also pin and test the Laravel and Symfony Process versions you deploy.
- Can I run database backups on a Laravel queue with this package?
- Queue safety is not established by the release notes provided; process handles are generally not serializable across worker restarts. Validate the package's behavior before dispatching backups as queued jobs. A safer pattern is to schedule the Artisan command or wrap it in a job that handles failures and cleanup explicitly.
- How should I test laravel-database-backup before relying on it?
- Run the backup command manually in staging, confirm the dump file exists, and restore it into a scratch MySQL database to prove integrity. Test failure paths such as bad credentials, a missing dump binary, unwritable storage, and mail delivery errors. In CI, exercise the exact Laravel and Symfony Process version combination you plan to run in production.
- What are alternatives to jpbgomes/laravel-database-backup?
- Spatie's laravel-backup is the common broader alternative, covering multiple filesystems, cleanup policies, and notifications beyond a MySQL dump. This package is a simpler fit if you specifically want MySQL backups plus email and schedulable Artisan commands. Compare maintenance activity, tested Laravel versions, and restore workflow before choosing.