- Can I install madalynn/plum-bundle in a Laravel application?
- No. PlumBundle is a Symfony2 bundle that registers a Symfony Bundle class and wires services through Symfony's DI container, and Laravel has no boot path for that model. Composer will likely also refuse to resolve it because of its PHP 5.x and Symfony 2.x constraints. Treat it as unusable in a Laravel app and invoke the Plum CLI directly instead.
- Does madalynn/plum-bundle support Laravel 10 or 11?
- No. Laravel 10 and 11 require PHP 8.1 or newer, while this bundle pins PHP to 5.x and early 7.x alongside Symfony 2 components that reached end of life in November 2018. Installing it next to a current Laravel release either fails Composer resolution or forces an application-wide downgrade. There is no supported combination of this bundle and a modern Laravel version.
- What PHP versions does madalynn/plum-bundle require?
- The bundle targets PHP 5.x and early 7.x, matching its Symfony2 era. That predates every Laravel release that still receives security fixes, so you should expect a hard conflict on PHP 8.1 and above. Check the exact constraint in its composer.json before assuming anything, but plan for incompatibility.
- Is madalynn/plum-bundle still maintained?
- There is no evidence of active maintenance. The repository is small with no dependents, so there is no downstream bug pressure to drive fixes, and Symfony2 itself has been end of life since November 2018. Adopting it transfers ownership of Symfony internals, including security patching, to your team, and issues are likely to go unanswered.
- How do I use Plum in a Laravel project without this bundle?
- Run Plum as a standalone CLI or PHAR and call it from a versioned script committed to your repo, then execute that script as a CI job or Makefile target. If you want it inside Laravel, write a small Artisan command that shells out to the Plum binary and returns its exit code. That keeps the deploy logic in Plum and avoids carrying an end-of-life Symfony bundle.
- What is the difference between a Symfony bundle and a Laravel service provider?
- A Symfony bundle extends Symfony's Bundle class and wires services through the Symfony DI container and Console component. Laravel uses service providers, publishable config, and Artisan commands instead. The two have no shared boot path, so a bundle cannot simply be composer-required into a Laravel app, and porting one to the other is a rewrite rather than an integration.
- What are Laravel-friendly alternatives to madalynn/plum-bundle for deployments?
- Laravel Envoy and Deployer are the usual recipe-based choices, while Forge, Envoyer, or Vapor cover managed deploys. Any of them can invoke the Plum CLI if Plum's release model is genuinely required. Start with whatever your platform already provides before adding another tool to the stack.
- Can I use madalynn/plum-bundle with Laravel Sail or Vapor?
- No. Sail and Vapor run modern PHP and Laravel, which conflicts with the bundle's PHP 5.x and Symfony2 constraints. Vapor in particular expects Laravel-native entry points and has no concept of a Symfony bundle. Use Plum standalone or a platform-native deploy path instead.
- How do I test an Artisan command that calls the Plum CLI?
- Use Orchestra Testbench or a feature test that runs the command, and fake the underlying process with Process::fake() or a thin wrapper interface so no real deploy executes. Assert the exit code and the exact arguments passed to Plum. Keep the Plum call behind a small class so tests do not depend on the binary being installed.
- Is madalynn/plum-bundle safe for production, or should I fork it into a Laravel package?
- Not in a modern Laravel stack, and forking is not proportionate. The bundle is a 26-star wrapper with no dependents and no production validation behind it, so a port would be a rewrite of code that has never carried real traffic. Production use only makes sense inside an inherited Symfony2 application you already maintain; if Plum's release model is the real requirement, call the binary from CI and skip the bundle entirely.