- What does vincentbean/horizon-extended-dashboard do?
- It is a Laravel package that extends the Horizon dashboard with additional queue and job insights. Built with Livewire, it helps you monitor workers, inspect workloads, and debug Redis-backed queues. It is a drop-in addition for applications already using Laravel Horizon. It does not alter your core queue architecture.
- How do I install vincentbean/horizon-extended-dashboard?
- Install it via Composer with composer require vincentbean/horizon-extended-dashboard. Then publish the package config and assets as described in the repository. No database migrations or infrastructure changes are implied. It fits into existing Laravel and Horizon deployments with low friction.
- Does this package require Laravel Horizon?
- Yes, the package extends the Laravel Horizon dashboard, so your application needs Horizon installed and configured. It is designed as a drop-in addition for Horizon users. The extended views complement Horizon rather than replacing it.
- Which Laravel and Horizon versions are supported?
- It should work with the current Laravel and Horizon versions allowed by the package's Composer constraints. You should confirm those constraints against your application's Laravel version before upgrading. Release 1.2.2 is a feature enhancement with no breaking API changes.
- Does it support queued Mailables in the dashboard?
- Yes, release 1.2.2 adds support for queued Mailables as queue items in the extended dashboard. Laravel queued mailables are dispatched as jobs, so they now appear as first-class items. This addition is additive and does not require changes to existing job or queue definitions.
- Do I need to run migrations or change queue config?
- No, there are no database migrations or infrastructure changes implied. You install via Composer and publish config/assets as needed. Existing Horizon monitoring practices remain valid after installation.
- Will it impact queue performance or worker scaling?
- It has no direct impact on queue throughput or worker scaling. Dashboard rendering may see slightly more data for Mailable jobs, but this is expected to be negligible unless Mailables carry very large payloads. Your existing Horizon monitoring and scaling practices remain valid.
- What happens if a queued Mailable fails to deserialize?
- If Mailable deserialization fails, the dashboard might show errors for those queue items. Ensure that queued Mailables are autoloadable in the environment where the dashboard runs. This does not impact actual mail delivery, only dashboard rendering.
- How do I upgrade to get Mailable support?
- Run composer update vincentbean/horizon-extended-dashboard to upgrade. Existing dashboards continue to work, and Mailable queue items will now be recognized or rendered where previously they may have appeared as generic jobs. No config changes are needed unless you want to filter or customize Mailable display.
- Is the package tested for Mailable rendering and deserialization?
- Test coverage for Mailable rendering and deserialization in the dashboard context is unknown. The technical risk is low because this is an additive feature, but you should verify queued Mailables appear correctly in staging. Monitor upstream releases for compatibility with future Laravel and Horizon versions.