Weave Code
Database Commands Bundle Laravel Package
abmundi/database-commands-bundle
Symfony bundle to automate MySQL database dumps and imports via a db:dump console command and Capifony tasks. Creates timestamped dumps (with hard link to latest), supports download from remote and import into local production/testing environments.
At a glance
Frequently asked questions about Database Commands Bundle
- Can I use abmundi/database-commands-bundle in Laravel for database dumps?
- No, this bundle is Symfony-specific and relies on Symfony’s Console component and Capifony tasks, which are incompatible with Laravel’s Artisan CLI. Laravel already has native tools like `artisan db:dump` or packages like `laravel-backup` for similar functionality.
- What Laravel alternatives exist for MySQL dump/import automation?
- Use `laravel-backup` for scheduled backups, custom Artisan commands for mysqldump wrappers, or Deployer for deployment workflows. These avoid Symfony dependencies and integrate seamlessly with Laravel’s ecosystem.
- Does this bundle support remote database dumps like Capifony?
- The bundle includes Capifony tasks for remote dumps/downloads, but Capifony itself is Symfony-only. Laravel uses Deployer, Forge, or Envoyer for deployment tasks—rewriting these tasks for Laravel would require significant effort.
- Will this bundle work with Laravel’s database connections (e.g., MySQL, PostgreSQL)?
- No, the bundle assumes MySQL CLI tools (`mysqldump`, `bunzip2`) and Symfony’s Console. Laravel’s database abstraction (e.g., `DB::connection()`) and Eloquent migrations are incompatible with its hardcoded CLI workflows.
- How do I replicate the `db:dump` command in Laravel?
- Create a custom Artisan command wrapping `mysqldump` or use `laravel-backup` for pre-built functionality. Example: `php artisan make:command DumpDatabase` and extend it with your dump logic.
- Are there performance benefits to using this bundle over Laravel-native tools?
- No, the bundle doesn’t offer unique optimizations for large databases or remote backups. Laravel’s `laravel-backup` or custom scripts can achieve the same results without Symfony’s overhead.
- What are the risks of integrating this Symfony bundle into Laravel?
- High risks include framework lock-in, dependency bloat (Symfony autoloader/Kernel), and operational friction (requiring `mysqldump`, `bunzip2` across environments). Maintenance becomes unsustainable over time.
- Can I use this bundle’s Capifony tasks in Laravel with Deployer?
- No, Capifony tasks are tightly coupled to Symfony. Deployer uses PHP tasks, so you’d need to rewrite the logic manually or use Deployer’s built-in database commands.
- Is this bundle actively maintained or Laravel-compatible?
- The bundle is unmaintained (no stars, no dependents, `dev-master` dependency) and lacks Laravel integration. It’s designed for Symfony, not Laravel, and introduces unnecessary complexity.
- How do I ensure `mysqldump` and `bunzip2` are available in all Laravel environments?
- Use Docker containers with these tools pre-installed or leverage Laravel Forge/Envoyer, which handle dependencies. Avoid relying on global CLI tools, as they’re inconsistent across shared hosting or CI environments.
Weaver
How can I help you explore Laravel packages today?