- Does frcho/backup-manager work with Laravel 10 or 11?
- Very unlikely. The package is a Symfony2-era fork that pins symfony/console 2.x, league/flysystem 1.x, and an older AWS SDK generation, which conflicts with modern Laravel and PHP 8.2+. Composer require will probably fail, and making it work is a fork-and-modernize project rather than a dependency addition.
- How do I install frcho/backup-manager?
- The intended path is composer require frcho/backup-manager with manual service provider registration, since the package predates Laravel package auto-discovery. In practice, expect dependency resolution conflicts on current Laravel versions. If it installs at all, you will also need to publish and edit its config file for backup profiles and storage credentials.
- Does frcho/backup-manager support restoring backups?
- There is no documented restore primitive, and the evaluation found no tested restore path. A backup tool whose restore is unverified is a compliance artifact rather than a recovery capability. Treat restore as unsupported unless you audit and test the source yourself.
- What storage destinations does frcho/backup-manager support?
- It advertises Amazon S3, Rackspace Cloud Files, Dropbox, FTP, and SFTP through bundled Flysystem 1.x adapters. Dropbox v1 is retired and Rackspace Cloud Files is effectively end-of-life, leaving S3, FTP, and SFTP, all of which Laravel filesystem disks already cover with maintained adapters. Driver relevance is therefore uneven.
- Is frcho/backup-manager maintained and safe for production?
- The repository shows 0 stars, 0 dependents, and no upstream activity, and it is a fork of an already-abandoned backup-manager. There is no CVE watch, issue triage, or realistic path to upstream fixes. Running it with production database credentials and cloud storage keys carries significant supply chain risk.
- Can I schedule frcho/backup-manager backups with Laravel's scheduler?
- The package does not integrate with Laravel's scheduler natively; it expects manual or cron invocation. You could wrap its command in Schedule::command if the command runs under your Laravel version, but that is a workaround, not first-class integration. It also provides no events, health checks, or failure notifications for alerting.
- What are good alternatives to frcho/backup-manager for Laravel?
- spatie/laravel-backup plus Laravel filesystem disks is the standard Laravel-native alternative. It supports backup:run and backup:monitor, events, notifications, health checks, a documented restore path, and maintained S3, SFTP, and FTP adapters. Unless you have a hard legacy or air-gapped requirement, it satisfies the same operational concern with far less risk.
- Does frcho/backup-manager support PHP 8.2?
- No, that is very unlikely. The Symfony2-lineage code pins PHP to the 5.5 through 7.x range along with symfony/console 2.x and Flysystem 1.x. Supporting PHP 8.2 would require a fork-and-modernize effort, including adapter and dependency replacements.
- How does frcho/backup-manager handle database credentials and log redaction?
- This is unverified. Shell command construction for mysqldump and pg_dump, credential redaction in logs and exception traces, retention and deletion semantics, and encryption at rest are all undocumented. Each is a plausible incident vector, so audit the source before letting it handle production secrets.
- Can frcho/backup-manager back up files and directories, or only databases?
- The blurb mentions directory archives, but the technical evaluation found the advertised scope to be database backup only. There is no verified restore path for either databases or files. Confirm capabilities directly in the source before relying on file backups.