- Can I use pwt777/pheanstalk-bundle in a Laravel application?
- No. It is a Symfony2 bundle that relies on Symfony's DI container, Bundle class registration, and console component, none of which Laravel's service container understands. Any Laravel integration would mean bypassing the bundle and consuming the underlying pda/pheanstalk client directly, at which point the package adds no value. Use Laravel's native beanstalkd queue driver instead.
- What does pwt777/pheanstalk-bundle actually do?
- It wraps the Pheanstalk PHP client for beanstalkd inside a Symfony2 bundle, exposing a Pheanstalk service through the DI container and adding console commands for Beanstalkd stats and tube operations. It was built for Symfony2 applications, not Laravel or modern Symfony. The genuinely reusable part is a thin CLI wrapper that is short enough to reimplement in a single Artisan command.
- How do I install pwt777/pheanstalk-bundle with Composer?
- You would normally run composer require pwt777/pheanstalk-bundle, but on a Laravel project this will almost certainly fail dependency resolution. The bundle expects Symfony2-era constraints for symfony/console and symfony/dependency-injection, which conflict with the newer Symfony components Laravel pins. Forcing it with --ignore-platform-reqs is a red flag rather than a workaround, and it still would not register with Laravel's container.
- Does pwt777/pheanstalk-bundle support Laravel 10, Laravel 11, or PHP 8.2?
- There is no evidence of support for any modern Laravel or PHP version. The last release was November 2021, there is no CI signal in the repository, and no PHP 8.1, 8.2, or 8.3 compatibility testing is documented. Symfony2 itself is end-of-life, so the transitive assumptions are frozen against a dead framework line.
- What is the Laravel equivalent of this Symfony bundle for beanstalkd?
- Laravel ships a first-party Beanstalkd queue driver backed by pda/pheanstalk and configured in config/queue.php. That driver gives you job dispatch, workers, retries, and failed-job handling without any Symfony bundle. For admin tasks like stats, peek, kick, and pause, write a small Artisan command using pda/pheanstalk directly.
- How do I configure a beanstalkd queue in Laravel without this bundle?
- Add a beanstalkd connection to config/queue.php, install pda/pheanstalk with Composer, and set QUEUE_CONNECTION=beanstalkd in your environment. Laravel's built-in driver handles the connection, worker, and retry semantics. Custom tube names and per-connection options are supported through the queue configuration array.
- Is pwt777/pheanstalk-bundle still maintained?
- No. The repository has one star, zero dependents, a single maintainer, and its last release was November 2021. There is no CI, no security disclosure process, and no downstream validation. Treat it as abandoned and pin the exact version if you inherit it in a legacy Symfony2 codebase.
- Can I migrate the bundle's Beanstalkd admin commands to Laravel Artisan?
- Yes, and that is the recommended path if you only need the CLI functionality. The bundle's useful surface is a thin wrapper around stats, peek, kick, and pause operations, which fits comfortably in a single app/Console/Commands/BeanstalkdAdmin.php. Encapsulate calls behind a small interface so the console layer can be swapped without touching call sites. This typically takes about a day and leaves you with fully owned, testable code.
- Are there security or supply-chain risks with using this abandoned package?
- Maintenance risk is high because an abandoned package with no dependents is a soft target for account takeover or typosquat drift, and any future revival release would be effectively unreviewed. The MIT license and small code surface limit legal and audit exposure but do not offset that risk. Supply-chain risk is moderate rather than severe, but there is no reason to accept it in a greenfield Laravel project.
- What alternatives should Laravel developers consider instead of this bundle?
- Start by confirming whether you actually need beanstalkd specifically or just a durable work queue, since Laravel already supports Redis, SQS, and database drivers out of the box. If beanstalkd is a hard requirement, use pda/pheanstalk directly with Laravel's native beanstalkd queue connection. For admin tooling, port the handful of stats and tube commands into your own Artisan command rather than installing a Symfony2 bundle.