- How do I install arxeiss/sansdaemon in a Laravel app?
- Install it with Composer using composer require arxeiss/sansdaemon, then optionally publish the package config file if the README documents one. It is a small, single-purpose utility that typically registers a console command or scheduler hook rather than restructuring your application. Confirm the exact install and publish steps against the README for the specific version you install, since the package is at v1.3.2 and documentation is the primary reference.
- Does Sansdaemon really process Laravel queues without a daemon?
- Yes, that is the core idea: the worker is invoked from cron or Laravel's scheduler, drains available queued jobs, and then exits instead of staying resident like queue:work. This suits shared hosting, PaaS instances, and small deployments where Supervisor or systemd units are awkward to run. The trade-off is throughput and worker semantic fidelity, so treat it as a complement to a daemon worker rather than a drop-in replacement for horizontally scaled workers.
- Which Laravel and PHP versions does Sansdaemon support?
- The v1.3.2 release widened the framework compatibility constraint to include Laravel 13, which is the only functional change in that patch release. Because Laravel 13 likely requires PHP 8.3 or newer, check the package's composer.json for the exact php and illuminate/* constraints before upgrading. Verify the claim against a CI matrix that actually runs tests on your target Laravel version, not just a widened constraint.
- How do I schedule the Sansdaemon worker with cron or the Laravel scheduler?
- Add the package's worker command to your scheduler or a cron entry so it runs every minute and exits after draining the jobs currently available. This assumes schedule:run is already running reliably in your environment; if it is not, set that up first, because it is a prerequisite rather than part of the package. Watch for overlapping runs, and check how the package guards against two scheduled invocations processing the same queue at once.
- How does Sansdaemon handle retries, backoff, timeouts, and failed jobs?
- This is the area to verify before adopting, because a process-per-run model frequently diverges from queue:work semantics. Retry counts, backoff, timeouts, tries, and failed-job handling depend on which Laravel queue contracts and command options the package exposes. Test those behaviours explicitly on a staging queue with deliberately failing and slow jobs rather than assuming parity with the daemon worker.
- Can I use Sansdaemon with the database, Redis, or SQS queue drivers?
- The queue driver choice is largely orthogonal, since the package triggers job processing and the connection is still defined in config/queue.php. Confirm which drivers the README documents as supported before committing, because some driver features assume a resident worker. Database and Redis are the usual candidates for low-volume queues drained on a schedule.
- Is Sansdaemon suitable for high-throughput production queues?
- It is best suited to low-to-moderate throughput queues on cost-sensitive or constrained hosting, where avoiding Supervisor is a real benefit. If you need horizontal worker scaling, tight throughput targets, or precise retry and backoff guarantees, keep queue:work under Supervisor or use Horizon. Those limits come from the no-daemon model itself rather than from defects in the package.
- Does Sansdaemon work with ShouldBeUnique and WithoutOverlapping jobs?
- Those features rely on Laravel's cache locks, and their behaviour needs verification if the package does not delegate to the standard queue worker. Test unique and overlapping job classes directly against the package in staging before relying on them in production. If locks or overlapping guards misbehave, keep those specific jobs on your existing daemon worker.
- Is Sansdaemon actively maintained, and what are the alternatives?
- It is a single-maintainer package with low pull-request volume and recent releases dominated by a compatibility bump, so assume a bus factor of one and no support SLA. The alternatives are queue:work under Supervisor or systemd, Laravel Horizon for Redis queues, or a managed queue runner. The package makes sense where a daemon is genuinely inconvenient, not where vendor support or security response commitments matter.
- How do I remove Sansdaemon cleanly if I stop using it?
- Because integration is config-level, rollback is usually just re-enabling your existing queue:work worker and removing the scheduler entry. Check whether the package persists any state, such as database tables, cache keys, or locks, that would survive a composer remove. Keeping Supervisor unit definitions in the repo during any pilot keeps reverting cheap and fast.