- Does mcfedr/beanstalk-queue-driver-bundle work with Laravel?
- No. It is a Symfony bundle built around Symfony's Kernel, DI container, and config/bundles.php registration model, so it has no service provider or config/queue.php hook for Laravel. Laravel already ships a first-party beanstalkd driver via pda/pheanstalk behind the Illuminate\Contracts\Queue\Queue contract, so installing this bundle in a Laravel app would add a dependency without adding capability.
- What is mcfedr/beanstalk-queue-driver-bundle used for?
- It is a Symfony bundle that provides a Beanstalkd queue driver for the mcfedr queue manager, letting Symfony applications offload background work to Beanstalkd tubes through the mcfedr queue abstractions. It wires producer and consumer services into Symfony's service container and exposes configurable connection and tube settings. It is glue for the mcfedr/beanstalk-queue-driver and the broader mcfedr queue stack, not a standalone Laravel package.
- How do I install mcfedr/beanstalk-queue-driver-bundle?
- Install it with Composer and register it in a Symfony application's config/bundles.php as you would any Symfony bundle. You will also need the mcfedr queue manager and driver packages that this bundle is designed to wire together. There is no Laravel package discovery support, so it will not self-register in a Laravel app.
- Which Symfony and PHP versions does this bundle support?
- The provided context does not state supported Symfony or PHP majors, the last release date, or current commit activity. Check the repository's composer.json constraints and release history before assuming it installs cleanly on your runtime. For a Laravel application this question is moot because the bundle is not a Laravel package.
- How do I configure the Beanstalkd connection and tube settings?
- The bundle exposes configurable connection and tube settings through standard Symfony bundle configuration and DI extension wiring. You configure the Beanstalkd host, port, and tube names in your Symfony config, and the bundle maps producer and consumer services onto those tubes. Exact option names should be taken from the bundle's DI extension and README rather than assumed.
- Is mcfedr/beanstalk-queue-driver-bundle safe for production?
- Treat it as high supply-chain risk: the context reports 1 star, 0 dependents, a package score of 0.005, and a single maintainer. That means no downstream consumers exercising it in production and no real-world regression coverage. The code volume is small and the MIT license is permissive, but adoption implies fork-and-maintain rather than vendor support.
- What dependencies does mcfedr/beanstalk-queue-driver-bundle require?
- It is glue for mcfedr/beanstalk-queue-driver, and the sibling mcfedr/queue-driver interface plus mcfedr/queue-manager-bundle are effectively required context. That makes it a multi-package, single-vendor stack. Laravel's native beanstalkd support, by contrast, is a single config line backed by pda/pheanstalk.
- Can I use this bundle as a reference for a Laravel Beanstalkd driver?
- Yes, but only as a design reference. Reading its DI extension and service definitions can show how producer and consumer wiring and tube pinning are mapped declaratively. Do not vendor it into Laravel to build a driver, because that means re-implementing a ConnectorInterface and Queue implementation around a package that offers nothing over the native driver.
- How does this compare to Laravel's native beanstalkd queue driver?
- Laravel's native driver uses pda/pheanstalk behind the Illuminate\Contracts\Queue\Queue contract and includes queue:work, failed_jobs, and job-envelope handling out of the box. This bundle is a Symfony integration for the mcfedr queue manager and provides no Laravel service provider or config/queue.php hook. For a Laravel app, set QUEUE_CONNECTION=beanstalkd and configure config/queue.php instead.
- What are the alternatives to this bundle for Beanstalkd queues?
- For Laravel, use the first-party beanstalkd driver with pda/pheanstalk and configure config/queue.php. For Symfony, a hand-rolled pheanstalk service definition is roughly a day of work and avoids a single-maintainer dependency. If you need managed queuing, consider a managed broker and keep an exit path rather than adopting an unvalidated bundle.