- What is vuthaihoc/moox-jobs?
- vuthaihoc/moox-jobs is a Laravel package that adds a Filament plugin for managing job queues, failed jobs, and batches. It gives you an admin panel UI for job-related records instead of jumping between Artisan commands and database tables. It is positioned as a lightweight starting point that follows Laravel's existing conventions without extra boilerplate.
- How do I install moox-jobs with Composer?
- Install it with Composer using composer require vuthaihoc/moox-jobs. Then register the plugin in your Filament panel provider following the package README, since Filament plugins are attached per panel. Clear cached config and assets as you normally would for a Filament plugin, and confirm the new pages appear in your panel navigation.
- Does moox-jobs require Filament?
- Yes. The package is described as a Filament plugin, so you need a Laravel application with Filament installed and at least one configured panel. It is not a standalone queue dashboard and will not render without Filament.
- Which Laravel versions does moox-jobs support?
- The provided overview does not list explicit Laravel or Filament version constraints, so check the package's composer.json and README before requiring it. Because it integrates as a Filament plugin, your Filament major version is the most important compatibility factor. Test the install on a staging branch if you are running a recent Laravel release.
- Can moox-jobs retry failed jobs from the admin panel?
- The plugin is specifically described as managing failed jobs, so expect a Filament resource for browsing failed job records. Typical actions in such UIs include inspecting the exception payload and retrying or deleting a job, but confirm the exact actions in the README. This gives you a point-and-click alternative to the queue:failed and queue:retry Artisan commands.
- Is moox-jobs a replacement for Laravel Horizon?
- No. Laravel Horizon is a Redis queue manager and worker supervisor, while moox-jobs is a Filament admin UI for jobs, failed jobs, and batches. They solve different problems and can be used together if you run Redis queues and want a panel for inspection.
- Does moox-jobs work with the database queue driver or only Redis?
- Laravel's queue system is driver-agnostic and this plugin reads job-related records through the application, so it is not tied to Redis the way Horizon is. Database-backed queues and other drivers should be usable as long as the relevant job and failed job tables exist. Verify behaviour with your specific driver in staging.
- Is moox-jobs actively maintained and safe for production?
- The repository is marked READ-ONLY, which suggests it is not under active feature development. That does not stop you from using or forking it, but review the code, pin the version in composer.json, and plan for maintenance. Treat it like any small third-party admin plugin and test upgrades carefully before production.
- How do I test moox-jobs in my application?
- Check the repository for a test suite and run composer test or vendor/bin/phpunit if one is provided. Because the plugin is UI-focused, also do a manual smoke test in a staging panel: open the queue pages, dispatch a dummy job, force a failure, and confirm batches render. That covers the paths most likely to break during upgrades.
- What are some alternatives to moox-jobs?
- Alternatives include Laravel Horizon for Redis queue monitoring and worker supervision, Laravel Telescope for inspecting dispatched jobs and exceptions, and the built-in queue:monitor and queue:failed commands. If you want a Filament-native experience, you can also build custom Filament resources over the jobs and failed_jobs tables. moox-jobs is a lightweight option when you want those screens without writing them yourself.