- Is rch/capistrano-bundle a Laravel package?
- No. It is a Symfony2+ bundle that wires Capistrano deployment recipes into a Symfony application, and its architecture assumes a Symfony kernel, console, and directory layout. It does not ship Laravel recipes or reusable Laravel deployment logic.
- How do I install rch/capistrano-bundle?
- It is installed with Composer as rch/capistrano-bundle, but installation is not recommended for new projects. The last release was 2016-06-18, so dependency resolution on modern PHP and Symfony versions will likely fail. If you must inspect it, pin it in an isolated environment and review the license first.
- Does rch/capistrano-bundle support Laravel 10 or Laravel 11?
- No. The package predates those Laravel versions and targets Symfony2+, so it provides no Artisan migrate, queue restart, Horizon, or Octane deployment tasks. Using it with Laravel 10 or 11 would mean writing your own Capistrano task graph from scratch.
- What PHP and Symfony versions does rch/capistrano-bundle support?
- The 2016 release implies PHP 5.x/7.x-era constraints and Symfony 2.x/3.x coupling, though you should verify exact constraints in composer.json. On PHP 8.2 or 8.3 the resolver will likely fail or require ignore-platform-reqs workarounds. Modern support would require a fork and upgrade.
- How do I configure rch/capistrano-bundle for a Laravel app?
- You cannot get meaningful Laravel configuration from the bundle because it assumes Symfony conventions for cache warmup, console commands, assets, and parameters. A Laravel setup would need hand-written deploy.rb and rake tasks for migrations, queues, and release signals. At that point the bundle adds no reusable Laravel value.
- How should I test deployments if I fork rch/capistrano-bundle?
- Test on a staging server or disposable VM that matches production OS, Ruby, PHP, and web server versions. Run cap staging deploy, verify the release symlink, migrations, cache warmup, queue restarts, and rollback behavior. Because the bundle is Symfony-oriented, Laravel task coverage must be tested separately after you write it.
- Is rch/capistrano-bundle maintained?
- No. There has been no release since 2016-06-18, with roughly 11 stars and zero dependents, and there is no observable maintainer triage or security response. Treat it as unowned code and plan to fork and maintain it indefinitely if you adopt it.
- What license is rch/capistrano-bundle released under?
- The declared license is NOASSERTION, meaning it could not be machine-identified as a standard SPDX license. Legal review is required before production use, and ambiguous licensing is a blocker for many enterprises. Inspect the repository manually rather than assuming a permissive license.
- What are the best alternatives to rch/capistrano-bundle for Laravel?
- Use a PHP-native or managed deployment path such as Deployer, Laravel Forge, Envoyer, Laravel Cloud, or GitHub Actions with container images. If you already run Capistrano, keep Capistrano and inline the needed tasks in config/deploy.rb and lib/capistrano/tasks instead of depending on this bundle. These options avoid the Ruby toolchain and abandonment risk.
- Should I use rch/capistrano-bundle in production?
- No, not for a Laravel application. The bundle is abandoned, license-ambiguous, built for Symfony2+, and adds a Ruby toolchain without providing reusable Laravel logic. Production use would introduce unresolved dependency, security, and maintenance risk.