Weave Code
Backup Laravel Package
nuewire/backup
A Laravel package for backing up your application, giving you a simple way to capture and store backups from your project. Lightweight and easy to add to a Laravel app, it fits into existing workflows for keeping copies of your data safe.
nuewire/backup is a Laravel package for creating and managing backups of your application’s files and database. It integrates with Laravel’s scheduler and filesystem, making it easy to automate backups to local or cloud storage.
- Schedule file and database backups
- Store backups on any Laravel filesystem disk
- Configure retention and cleanup policies
- Run backups via Artisan commands
- Restore from existing backups
Frequently asked questions about Backup
- What is nuewire/backup used for in a Laravel application?
- nuewire/backup is a Laravel package for scheduled backups of your application database and, optionally, application files. It stores archives on local or cloud disks and manages retention so old backups do not accumulate indefinitely. It is powered by spatie/laravel-backup and is aimed at Nuewire applications that need routine, restorable backups.
- How do I install nuewire/backup in a Laravel application?
- Install it with Composer by running composer require nuewire/backup. Publish the package configuration as described in the README, then choose the backup disk and database settings. Run the backup Artisan command once to confirm an archive is created.
- Does nuewire/backup back up only the database or files as well?
- It supports both database-only backups and database-plus-file-storage backups. Use database-only mode when the database is the critical state, or enable file storage when uploads and other application files must be captured too. Review the package config for how file paths are included.
- Which Laravel versions are supported by nuewire/backup?
- The provided package context does not list specific Laravel version constraints. Check composer.json and the README for supported Laravel and PHP versions before installing. Because it depends on spatie/laravel-backup, also confirm that dependency supports your Laravel version.
- Where does nuewire/backup store backup archives?
- Archives are stored on local or cloud disks configured through Laravel's filesystem settings. Point the package at the disk you want to use, such as local storage or an S3-compatible disk, and ensure write credentials are correct. Retention and cleanup then apply to that disk.
- How do I schedule nuewire/backup backups?
- Schedule the package's backup Artisan command with Laravel's scheduler, either in routes/console.php on newer Laravel versions or in the console kernel on older versions. Set the schedule to match your recovery point objective and make sure the scheduler is running in production. Consult the README for the exact command name and required options.
- How does retention work for nuewire/backup archives?
- Retention is managed through package configuration and the underlying backup cleanup workflow. Configure how many recent archives to keep so older backups are removed automatically. Check the published config for the exact retention keys and ensure cleanup runs on a schedule.
- Can I test nuewire/backup safely without production storage?
- Use a local filesystem disk and a staging or disposable database, then run the backup command manually and inspect the archive. Verify that the database dump exists and that file-storage mode includes the expected files. After that, test the same flow against your cloud disk in staging.
- Is nuewire/backup an alternative to spatie/laravel-backup?
- nuewire/backup is powered by spatie/laravel-backup, so it is best viewed as a Nuewire-oriented layer rather than a completely separate backup engine. Use it if its configuration and Artisan workflow fit your application; use spatie/laravel-backup directly if you want the upstream package without extra conventions. Compare both on storage drivers, retention, and restore process.
- How do I restore a backup created by nuewire/backup?
- Backups are archives containing the database dump and, when enabled, application files. Retrieve the archive from your configured disk, extract any file payload, and import the database dump into the target environment. Check the README for any package-specific restore command or workflow before relying on it in an incident.
Weaver
How can I help you explore Laravel packages today?