Weave Code
Radish Bundle Laravel Package
jadu/radish-bundle
Symfony bundle that integrates the Radish Redis client, letting you configure connections and clients through the service container and inject them into your services, commands, and controllers.
jadu/radish-bundle is a PHP Symfony bundle that wraps Radish in a reusable, Composer-installable package. It reduces integration boilerplate by registering required services and exposing configuration through Symfony’s standard bundle conventions, so teams can add Radish to an application with minimal setup.
- Installs cleanly via Composer
- Registers services automatically in the DI container
- Supports configurable bundle options
- Fits existing Symfony project structure
- Encourages reusable, modular package design
Frequently asked questions about Radish Bundle
- Is jadu/radish-bundle a Laravel package?
- No. jadu/radish-bundle is a Symfony bundle that provides service wiring, configuration defaults, and Twig helpers around Jadu's Radish Redis-backed job queue. It assumes a Symfony kernel, Symfony DependencyInjection, and Symfony Console, so it cannot be dropped into a Laravel application as-is. Laravel developers should evaluate the underlying Radish library rather than the bundle.
- Can I install jadu/radish-bundle in a Laravel application?
- There is no direct path. Laravel has no bundle registration mechanism and uses Illuminate\Container rather than Symfony DI. You would need to run a Symfony runtime somewhere in your stack or bypass the bundle entirely. For Laravel-first teams, the realistic options are a Symfony sidecar, a library-only port wrapped in a service provider, or not integrating at all.
- How do I use Radish with Laravel without the Symfony bundle?
- Depend on the Radish core library and hand-write an Illuminate\Support\ServiceProvider that binds queue, producer, and consumer services into Laravel's container. You can publish configuration and wrap radish:worker semantics in an Artisan command. This is feasible but the wrapper becomes your code to maintain, and you inherit Radish's queue semantics wholesale.
- Does jadu/radish-bundle support Laravel 10 or Laravel 11?
- No. The package targets Symfony, not Laravel, so Laravel version support is not applicable. What matters is its compatibility with current Symfony and PHP versions, which you should verify before considering a Symfony sidecar. Any Laravel version question really becomes a question about your own integration layer.
- What is the difference between Radish and Laravel's Redis queue?
- Radish is Jadu's Redis-backed job queue with its own producer, consumer, and worker command conventions. Laravel's native queue abstraction with the Redis driver, optionally Horizon, already covers producers, workers, retries, backoff, failed-job storage, and supervision. That overlap means most of Radish's surface area is already available natively in Laravel with better tooling visibility.
- Is jadu/radish-bundle safe to use in production?
- Treat it with caution. It has zero stars, zero dependents, and no community vetting, so there is no third-party security review, CVE history, or Stack Overflow corpus. The bus factor is one team at one vendor, and the 2024-12-06 release has not been shown to be a substantive change rather than a dependency bump. It is MIT licensed, so there is no legal obstacle, but operational risk is high.
- What are the alternatives to jadu/radish-bundle in Laravel?
- The lowest-risk alternative is Laravel's native Redis queue, with Horizon if you want supervision and dashboards. If you specifically need Radish semantics, port the core library behind a Laravel service provider instead of using the bundle. You can also run the bundle as a Symfony sidecar sharing Redis, but that adds a second framework and deploy pipeline for a single queue.
- How do I install and configure jadu/radish-bundle in Symfony?
- Install it with Composer and register the bundle in your Symfony kernel, then configure its service definitions and Redis connection defaults. The bundle supplies service wiring, configuration defaults, and Twig helpers so Radish components can be dropped in with minimal setup. Exact configuration keys and worker command names should be verified against the repository and your Symfony version.
- Does Radish work with Laravel Horizon or queue:failed?
- No. Job payload serialization in Radish is opaque to Laravel's queue tooling, so you will not get Horizon introspection or queue:failed visibility for Radish jobs. If observability and failed-job management matter, that is a strong argument for Laravel's native Redis queue. A custom integration would need to build its own monitoring and failure handling.
- What delivery guarantees does Radish provide?
- The available assessment does not document them. It is unclear whether Radish offers at-least-once or at-most-once delivery, what visibility timeouts exist, whether dead-lettering is supported, and what Redis keys or structures it writes. Those details matter for production reliability and for any future migration off Radish, so ask Jadu directly before committing.
Weaver
How can I help you explore Laravel packages today?