- What Laravel and Filament versions does adrolli/filament-job-manager support?
- The package is a Filament plugin, and its 5.x line strongly suggests it tracks Filament 5, but confirm the exact supported Filament and Laravel majors in the README compatibility matrix before installing. Version alignment is the main feasibility gate for projects already on Laravel and Filament. If your Filament pin is older, check for a matching package branch.
- How do I install the Filament job manager plugin?
- Install via Composer with composer require adrolli/filament-job-manager, then register the plugin in your Filament PanelProvider. Publish the config and optionally the assets, and make sure your standard Laravel queue tables (jobs, failed_jobs, job_batches) exist. No custom queue driver or service container wiring is required.
- Does it replace Horizon or my queue workers?
- No. It is a thin Filament UI over Laravel's native queue tables and does not replace queue infrastructure, workers, or Horizon. It provides read and inspect views plus mutation actions such as retry and delete. Horizon-specific features like Redis metrics, tags, supervisord visibility, and throughput charts are out of scope.
- Can I control who can retry or delete failed jobs?
- Panel access alone is not enough for a tool that can mass-delete production jobs, so mutations should be gated by a Gate or Policy rather than just panel access. The technical evaluation flags this as a key risk and asks whether the package ships an authorization hook for view, retry, and delete. Verify this in staging and restrict retry and delete actions to a named ops group before promoting to production.
- Does it work with Redis, SQS, or only database queues?
- It reads Laravel's standard queue tables and failed_jobs table, so database queues are the most straightforward fit. Redis-backed queues still store failed jobs in failed_jobs, but SQS and Beanstalkd can diverge around payload inspection and retry semantics. Confirm your driver before relying on retry and payload views in production.
- Does it support Laravel job batches?
- Batch views are driven by the job_batches table and Laravel's batch APIs, so batch support requires that table to exist. If your application does not use Bus::batch, the feature is inert but harmless. Verify batch behavior against your queue driver and Laravel version.
- Will large payloads or stack traces break the page or leak secrets?
- Payload rendering is a flagged concern because large serialized payloads and stack traces can increase page memory use. Exceptions and payloads may also expose environment variables, tokens, or other secrets to anyone who can view the panel. Check whether the package truncates or redacts payloads and restrict access accordingly.
- Does it paginate and filter large failed_jobs tables?
- Noisy systems can have millions of rows in failed_jobs, so listing and filtering behavior matters for query cost. The evaluation specifically asks whether the package provides pagination and server-side filtering plus index guidance. Test against a realistic failed-jobs volume before enabling it in production.
- Is it safe to use in production with a small maintainer base?
- Adoption signal is weak relative to the blast radius of an admin tool that can retry and delete production jobs, and it is a single-maintainer project. The MIT license and the fact that the value is mostly UI over data you already own mitigate abandonment risk. Roll it out in staging first, run it alongside Horizon or existing tooling for a sprint, and keep retry and delete restricted initially.
- Does the plugin send telemetry or phone home?
- The technical evaluation raises telemetry and phone-home as an open question, so confirm this in the package source and README before installing. Also check the release cadence and issue-response history if maintenance risk matters to your team. Absent explicit evidence, verify rather than rely on package defaults.