- Is mcfedr/periodic-queue-driver-bundle compatible with Laravel?
- No. It is a Symfony bundle that plugs into mcfedr/queue-manager-bundle and expects Symfony's dependency injection container, bundle registration, and kernel bootstrapping. Laravel's service providers and the Illuminate\Queue\Connectors\ConnectorInterface contract are a completely different abstraction, and there is no adapter shim. Treat this package as reference reading, not as a Laravel dependency.
- Can I install mcfedr/periodic-queue-driver-bundle with Composer in a Laravel project?
- Composer may resolve it, but it will not function inside Laravel. The package targets PHP 5.6/7.0 and Symfony 2/3, so constraint solving on PHP 8.x with Symfony 6 or 7 will almost certainly fail. Even if it installs, nothing in Laravel will register or boot the bundle. It is not a drop-in Laravel package.
- How do I schedule recurring queue jobs in Laravel without a cron entry per job?
- Use Laravel's native scheduler. Define the task once in app/Console/Kernel.php or routes/console.php with ->everyMinute(), ->withoutOverlapping(), and ->onOneServer(), and dispatch a job onto your existing queue. A single cron entry running schedule:run drives every recurring task, so you never need a separate cron per job. This is first-class, supported behavior.
- How is mcfedr/periodic-queue-driver-bundle configured for periodic job intervals?
- In a Symfony app you declare intervals in YAML or PHP config, and the bundle wires the driver through Symfony's dependency injection. There is no equivalent Laravel configuration because Laravel has no bundle registration, and the package's driver does not implement Laravel's queue connector contract. In Laravel, intervals are declared in the scheduler instead.
- Does this package support Laravel 11, PHP 8, or Symfony 6 and 7?
- No. The last release was 2017-09-29, targeting PHP 5.6/7.0 and Symfony 2/3. Modern dependency resolution will almost certainly fail, and the bundle-era APIs it relies on were removed in Symfony 6 and 7. There is no patching path, so any CVE in the transitive Symfony graph is unowned. Laravel version support is irrelevant because the package never targeted Laravel at all.
- Is mcfedr/periodic-queue-driver-bundle still maintained?
- Effectively no. It has roughly 1 star, 0 dependents, no production evidence, and no community triage. The bus factor is one with no recent activity. MIT licensing means you could fork it, but forking an abandoned 2017 Symfony bundle into a Laravel codebase transfers the entire maintenance burden to you on day one.
- Can I port the periodic scheduling logic from this bundle into a Laravel job or command?
- It is possible but rarely worth it. The scheduling logic is likely a few hundred lines, and you would be reading it as reference rather than depending on it. Timebox a spike only if a specific semantic, such as tick-based scheduling or periodic re-enqueue behavior, genuinely cannot be expressed by Laravel's scheduler. In most cases, rebuilding on the native scheduler is a half-day of work.
- What are the best alternatives to this package for periodic and scheduled jobs in Laravel?
- Start with Laravel's built-in scheduler and queue system, which cover recurring dispatch, overlap prevention, and single-server execution. For observability, add a maintained scheduler-monitoring package rather than a queue driver. If you need a pluggable queue abstraction, implement Laravel's Illuminate\Contracts\Queue\Queue contract directly.
- How do I test scheduled and periodic jobs in Laravel?
- Laravel provides scheduling assertions and queue fakes. You can assert that a scheduled event exists and runs at the expected interval, and use Queue::fake() to verify the job is dispatched. This gives you coverage for interval configuration, overlap prevention, and onOneServer behavior without a real worker or cron.
- Should I use this bundle or Laravel's scheduler for production recurring work?
- Use Laravel's scheduler. This bundle assumes Symfony full-stack conventions and has no overlap with Laravel's extension points, so bridging it is a rewrite rather than a wrapper. Running a Symfony bundle inside Laravel would mean hosting Symfony's DI and HttpKernel alongside Laravel, which is architecturally indefensible. Laravel's native scheduler plus the queue system covers the same use case with supported, maintained code.