- What is mad-web/nova-horizon-link used for?
- It is a Laravel Nova package that adds a navigation link from the Nova admin panel to your Laravel Horizon dashboard. It is a presentation-layer utility only: it does not add models, migrations, jobs, or queue infrastructure. It is useful when your application already runs Nova and Horizon and you want faster access to queue monitoring, failed jobs, and metrics. If Horizon is not deployed, the package has no consumer and should be skipped.
- How do I install mad-web/nova-horizon-link in Laravel Nova?
- Install it with Composer using composer require mad-web/nova-horizon-link inside a Laravel application that already has Nova and Horizon installed. The service provider is auto-discovered, so no manual registration is normally required. You can optionally publish the config file if the package ships one, then review the menu entry in your Nova panel. Validate the generated link in each environment before deploying.
- Which Laravel Nova versions does mad-web/nova-horizon-link support?
- The supported Nova, Laravel, and PHP versions are defined in the package's composer.json constraints, so check that file before adoption. Small Nova add-ons are often broken by Nova major upgrades because menu and tool contracts change between versions. Confirm whether the constraint is a caret range or an exact pin and whether a tagged release matches your Nova version. If your Nova major is not covered, treat the package as incompatible rather than assuming it will work.
- Does the Nova Horizon link respect Horizon's authorization gate?
- This is not confirmed by the package overview, so verify it in the source before relying on it. Horizon exposes an authorization gate, and a menu link that ignores it may be shown to users who will receive a 403 when they click through. If authorization-aware visibility matters in your admin panel, check how the package registers the menu entry and whether it calls the Horizon gate. Otherwise, implement the link in-house with the gate check you need.
- How does mad-web/nova-horizon-link resolve the Horizon URL?
- The package links to the Horizon dashboard, but the overview does not state whether it hard-codes /horizon, reads config('horizon.path'), or uses a route name. That distinction matters for subdirectory deployments, custom domains, and multi-tenant setups. Review the source to confirm the URL construction matches Horizon's own configuration semantics. If it hard-codes the path, expect broken links wherever Horizon does not live at the default location.
- Is it a Nova menu entry or a full Nova Tool with views and assets?
- Based on the assessment, it is a thin Nova menu or tool wrapper that registers a navigation entry pointing at Horizon. It does not appear to ship models, migrations, jobs, middleware, or runtime behavior beyond menu registration. Check the repository for compiled assets or views if you need to know whether a full Nova Tool is included. A menu-entry-only package is the lighter and more predictable option.
- Do I need to publish the config file for this package?
- Config publishing is optional according to the overview and is only needed if you want to override defaults. The package works with Composer install, provider auto-discovery, and a fixed link target. Publish and review the config in a feature branch so you can see exactly what is configurable. If there is nothing you need to change, you can skip publishing and rely on the defaults.
- Is mad-web/nova-horizon-link safe and maintained for production?
- The assessment describes it as single-maintainer, near-zero-adoption, and unversioned in the provided signals, with low blast radius. Failure is cosmetic, such as a dead link or missing menu entry, rather than a functional outage, so the downside is bounded and easy to revert. Check the commit history, last release date, and license before adopting it. For a production admin panel, weigh that supply-chain profile against writing the menu item yourself.
- Should I use this package or write the Nova menu link myself?
- A Nova menu item pointing at config('horizon.path') is a trivial in-house artifact with no supply-chain exposure. The package only earns its place if it correctly handles Horizon path prefixes, domains, and authorization-aware visibility in a way that saves you real work. Since both approaches take under an hour, make the build-versus-buy decision on supply-chain policy and maintenance, not effort. Document the call in an ADR if your team requires it.
- Does it work with multi-tenant or subdirectory Horizon deployments?
- That depends entirely on how the package builds the Horizon URL, which is not confirmed in the overview. A hard-coded /horizon link will fail behind a path prefix, a custom domain, or a per-tenant Horizon route. Test the generated link in local, staging, production, and any multi-tenant or subdirectory environment. If the package does not read Horizon's config or route name, prefer an in-house link that does.