Weave Code
Filament Forge Insights Laravel Package
prodstarter/filament-forge-insights
Filament Forge Insights brings Laravel Forge monitoring into your Filament admin panel, giving teams quick visibility into servers, sites, deployments, and key health metrics so you can spot issues and manage infrastructure without leaving your dashboard.
A read-only Laravel Forge integration for Filament that gives agencies and development teams a professional infrastructure dashboard they can safely share with clients.
Frequently asked questions about Filament Forge Insights
- What is prodstarter/filament-forge-insights used for?
- It is a read-only Laravel Forge integration for Filament that adds an infrastructure dashboard to your admin panel. It is aimed at agencies and development teams that want visibility into Forge servers, sites, deployments, and key health metrics without leaving Filament. The package is a presentation-layer plugin, not a replacement for Forge itself.
- How do I install filament-forge-insights in a Laravel Filament panel?
- Install it with Composer, register the plugin in a Filament PanelProvider, publish the config, and supply a Laravel Forge API token. Pin the exact package version and test in a non-production panel first. Register it in a single panel provider rather than globally, and keep the rollback path to one provider line plus composer remove tested.
- Which Filament and Laravel versions does filament-forge-insights support?
- The package overview does not publish a compatibility matrix, so check the composer.json constraint block first. Filament major-version compatibility matters because v3 to v4 changes have broken plugins before. Confirm the supported Filament, Laravel, and PHP versions with the maintainer before adopting it.
- Is filament-forge-insights safe to share with clients?
- The package is described as read-only and designed for client-facing infrastructure dashboards, so it reduces the risk of accidental changes. Safety still depends on how the Forge API token is scoped and stored and on who can access the Filament panel. Gate visibility behind a policy or permission rather than exposing it to every authenticated user.
- How is the Laravel Forge API token configured and stored?
- The provided overview does not document the token mechanism, but the plugin must authenticate to Forge with an API token. Treat this as a key evaluation question: confirm whether the token comes from environment variables, encrypted config, a service account, or another mechanism. Use a least-privilege token, store it in a secret manager, rotate it, and verify it is never exposed to the browser.
- Does filament-forge-insights cache Forge API responses or handle rate limits?
- The overview does not state whether the plugin makes live Forge API calls per page load or caches responses. Forge applies rate limits and has changed response shapes historically, so a polling plugin without caching can throttle or show stale data. Review the config for cache TTL and rate-limit handling before production use.
- What Forge insights and widgets does filament-forge-insights provide?
- The package overview lists servers, sites, deployments, and key health metrics inside a Filament dashboard. It does not enumerate every widget, so specifics such as SSL expiry, uptime, or deploy history need to be confirmed in the code or with the maintainer. Evaluate the actual v1.0.0 feature set before assuming coverage.
- Can I use filament-forge-insights without Filament?
- No. It is a Filament panel plugin and requires a Laravel application that already runs Filament. If your admin UI is not Filament-based, the package is not a fit regardless of its quality. Confirm Filament presence and version before evaluating it further.
- How do I control who can see Forge infrastructure data in Filament?
- Register the plugin in a single panel provider and gate its pages or widgets behind a Laravel policy or permission. Do not rely on panel login alone, because Forge data can reveal server names, site names, and deployment details. Restrict access to the roles that need infrastructure visibility and test those gates with real accounts.
- What are the production risks and alternatives to filament-forge-insights?
- The main risks are a broad-scope Forge token held by a presentation-layer plugin, an empty v1.0.0 changelog, a small publisher with bus-factor concerns, and Forge API rate-limit coupling. Pin the exact version, review the code and config, test rollback by removing the provider line and Composer requirement, and keep access behind authorization. Alternatives include the official Forge dashboard, a custom Forge API integration, or a more established monitoring tool if you need stronger maintenance guarantees.
Weaver
How can I help you explore Laravel packages today?