- Does fm/worker-bundle work with Laravel?
- It is a Symfony bundle built around Symfony's kernel, bundle registration, and dependency-injection container, so it does not integrate with Laravel's service providers or container conventions out of the box. Making it work in Laravel would require a bespoke bridge layer that your team would own and maintain. For Laravel applications, the native queue worker and Horizon already cover the same capability.
- Is fm/worker-bundle maintained or superseded?
- The package describes itself as superseded by treehouselabs/worker-bundle, so the maintainers have already routed users toward a successor. It has no stars, no dependents, and no visible downstream usage, which means there is no independent evidence of active maintenance. Superseded packages generally do not receive security patches or PHP and Symfony compatibility updates.
- What is the replacement for fm/worker-bundle?
- The stated successor is treehouselabs/worker-bundle. A successor existing does not by itself prove the replacement is healthy, so you should independently check its last commit dates, open issues, and dependents. If you are on Laravel, the stronger replacement is the framework's native queue system rather than another Symfony bundle.
- How do I install fm/worker-bundle?
- In a Symfony project you would install it with Composer, register the bundle in your kernel, and define workers through the bundle configuration. There is no Laravel service provider, config file, or publishable asset set, so running composer require in Laravel alone will not give you a working setup. For Laravel, installation is not the right question; use the native queue worker instead.
- What does fm/worker-bundle actually do?
- It provides a structured worker layer for Symfony applications: worker service registration in the DI container, configurable worker definitions, lifecycle handling for long-running processes, and extension hooks for logging or monitoring. That is a queue-daemon abstraction, not a queue backend. In Laravel the same surface is covered by queue workers under Supervisor or by Horizon.
- Which Laravel versions does fm/worker-bundle support?
- None in any supported sense. The package targets Symfony's kernel and bundle system, and there is no Laravel service provider or Laravel version constraint matrix. PHP-version overlap is the only common ground, so you should not plan Laravel version support around this package.
- What should Laravel teams use instead of fm/worker-bundle for background workers?
- Use Laravel's native queue worker with Supervisor for process management, or Horizon if you run Redis. Laravel already ships first-class queue drivers for Redis, SQS, RabbitMQ, and database queues. A managed queue service is also a valid replacement if you do not want to operate workers yourself.
- How do I migrate from fm/worker-bundle to Laravel queues?
- Treat it as an extraction, not an adoption. Inventory real usage by grepping for the bundle namespace, checking composer.lock, and reading configuration tree references, then map each worker and job definition to a Laravel Job class and queue connection. Run native workers in parallel in non-production and compare throughput, restart behavior, and failure modes. Cut over one queue at a time, never with a single flag day, and keep the old worker definition as a rollback for one release cycle.
- Is fm/worker-bundle safe for production?
- The main risks are abandonment and unverifiability. A superseded package will not get security patches, and zero dependents means there is no independent evidence that signal handling, child reaping, graceful shutdown, or restart-on-exit-code behave correctly under load. A lifecycle defect in a worker daemon shows up as silently stalled jobs and a growing backlog, which is high severity and low detectability.
- How do I test fm/worker-bundle worker lifecycle behavior?
- You would have to test it yourself, because there are no public dependents providing independent evidence. At minimum you would need coverage for signal handling, graceful shutdown, child process reaping, and restart behavior under load. Forking and daemon code is exactly where subtle defects hide, so this is expensive to validate. For Laravel teams, that effort is better spent on the native queue worker, which is already exercised by the framework and community.