- Is miksoftware/daemon-bundle compatible with Laravel?
- It is a Symfony bundle, not a Laravel package. The available assessment found no Laravel auto-discovery, service provider, facade, or publishable config, so it will not drop into a Laravel app idiomatically. You could hand-wire its classes inside an Artisan command, but treat that as a time-boxed spike rather than infrastructure.
- How do I install DaemonBundle with Composer?
- Installation would use Composer, but the bundle is registered through Symfony Kernel wiring rather than a Laravel service provider. Before running composer require, inspect its composer.json for PHP and Symfony component constraints and for required extensions such as pcntl and posix. In Laravel, expect manual wiring only if a spike proves value.
- What is the license for miksoftware/daemon-bundle?
- The assessment lists the license as NOASSERTION, meaning the terms are not machine-readable. Read the repository LICENSE file directly and have legal confirm commercial use, modification, and redistribution rights. Do not assume MIT or any permissive license.
- Does DaemonBundle replace Laravel Horizon or queue:work?
- No. Laravel already provides queue:work, schedule:run, and Horizon with graceful shutdown, timeouts, max-time, and restart semantics. DaemonBundle is a Symfony-oriented foundation for long-running worker commands and only makes sense for non-queue persistent workers where Laravel's queue semantics are awkward. Supervisor or Kubernetes should still handle process supervision.
- What PHP and Symfony versions does it require?
- The provided context does not specify exact version constraints. Check composer.json for the PHP floor, Symfony component ranges, and extension requirements, then compare them with your Laravel lockfile and container image. Also confirm Unix-only assumptions because pcntl is not available on Windows and may fail on non-POSIX CI runners.
- Does DaemonBundle handle graceful shutdown on SIGTERM?
- The overview advertises managed startup and shutdown plus graceful shutdown support, but the exit-code and in-flight-work contract is not confirmed here. Verify that it calls pcntl_async_signals(true) and dispatches signals correctly during deployment termination. Test SIGTERM behavior under load before trusting it in production.
- Is DaemonBundle production-ready for long-running PHP workers?
- The assessment rates technical risk high because the package has 5 stars, 0 dependents, a single maintainer, NOASSERTION licensing, and no visible CI or security signals. Long-running PHP adds known hazards such as memory growth, MySQL server has gone away, missed signals, and orphaned processes. Adopting a low-adoption library means your team owns debugging those hazards without community backup.
- Can I use DaemonBundle for queue consumers and scheduled tasks?
- It is positioned for daemon and worker commands, queue consumers, scheduled tasks, and other continuous jobs. For a Laravel team, queue:work and schedule:run remain the default, with Horizon where queue visibility matters. The bundle only earns a place for genuinely non-queue work such as a socket listener, streaming consumer, or persistent-connection poller.
- Are there tests and CI for miksoftware/daemon-bundle?
- The assessment reports no visible CI, security policy, or downstream validation signals. It also notes 5 stars, 0 dependents, and unclear release cadence, so code review is the due diligence. Confirm recent commits, test coverage, and a security policy in the repository before any adoption.
- How should a Laravel team integrate DaemonBundle safely?
- Run a time-boxed spike and wrap the dependency behind an internal DaemonRunner contract with run, stop, and tick methods if it proves differentiated value. Do not build that abstraction speculatively or position the bundle as core infrastructure. Keep Supervisor or Kubernetes responsible for supervision and be ready to swap in a Supervisor-managed Artisan command.