- Is hmillet/backup-commands-bundle a Laravel package?
- No. It is a Symfony bundle that relies on Symfony bundle registration, dependency injection extensions, and Symfony console commands. Laravel does not have a bundle concept, so the package will not auto-register, load configuration, or expose Artisan commands in a Laravel application. Making it work in Laravel requires a port, not a normal Composer install.
- Can I install hmillet/backup-commands-bundle in Laravel 10 or Laravel 11?
- It is unlikely to install cleanly. The last release was in March 2018, and its Symfony and PHP constraints are likely to conflict with the Symfony 6 or 7 components shipped by modern Laravel versions. Even if dependency resolution succeeds, the installed code will not integrate with Laravel's service providers or Artisan command system.
- What does hmillet/backup-commands-bundle actually back up?
- The package overview says it provides console commands for backing up application databases and files, with configurable dump paths, compression, and retention. The provided context does not confirm which database drivers, filesystem paths, or destination adapters are supported. You would need to inspect the source to verify the exact backup behavior before relying on it.
- Does hmillet/backup-commands-bundle support MySQL or PostgreSQL database dumps?
- The package claims database backup support, but the available context does not specify whether it shells out to native tools such as mysqldump or uses PHP database APIs. It also does not confirm which database engines are supported. This is a key detail to resolve by reading the command classes before considering any integration.
- How do I schedule hmillet/backup-commands-bundle backups in Laravel?
- You cannot schedule it directly in Laravel because it exposes Symfony console commands rather than Artisan commands. Laravel's scheduler expects Artisan commands or shell commands, so you would need to port the backup logic into a custom Artisan command first. A maintained Laravel backup package or an in-house Artisan command is the more practical path.
- Is hmillet/backup-commands-bundle maintained and safe for production?
- It has had no release since March 2018, has a single maintainer, one star, and zero dependents according to the technical assessment. That means there is no production usage signal, community security review, or recent PHP compatibility work. Backup tooling often receives database credentials and storage keys, so an unmaintained package is a poor choice for production.
- What PHP versions does hmillet/backup-commands-bundle support?
- A 2018-era Symfony bundle almost certainly declares PHP 7 constraints and old Symfony component versions. It is unlikely to install on PHP 8.2 or 8.3 without editing Composer constraints and patching the code. You should check composer.json and the command classes for removed PHP features before attempting any fork.
- What are the alternatives to hmillet/backup-commands-bundle for Laravel backups?
- For Laravel, use a maintained Laravel backup package or write a small set of Artisan commands that dump the database, archive files, push to Laravel's Storage disks, and prune old backups. The technical assessment estimates the equivalent functionality at roughly 150 to 300 lines of Laravel code. Both options are cheaper than owning a fork of an abandoned Symfony bundle.
- Does hmillet/backup-commands-bundle support retention, compression, encryption, and offsite storage?
- The overview mentions configurable dump paths, compression, and retention, but it does not confirm destination adapters, encryption, or integrity verification. The technical assessment lists those as open questions that require source review. For Laravel, offsite storage is better handled through the Storage facade and a maintained backup package.
- Can I fork hmillet/backup-commands-bundle and convert it to Laravel Artisan commands?
- You can, but it is a fork-and-own exercise rather than a normal integration. You would replace the bundle's dependency injection wiring with a Laravel service provider and config file, then reimplement each Symfony console command as an Artisan command. You would also need to verify that the underlying backup logic is separable and maintain PHP compatibility yourself. In most Laravel projects, writing the equivalent functionality in-house or adopting a maintained package is cheaper.