- What does gijsg/system-resources do?
- It is a Laravel Nova card that shows host system resource usage inside the Nova admin panel. The card gathers load average, memory, and disk metrics at request time and renders them as a dashboard tile via a Vue component. It does not store history, set thresholds, or send alerts.
- Does gijsg/system-resources support Laravel Nova 4 or Nova 5?
- The published release dates to May 2020, which places it in the Nova 3 era. Nova 4 moved card assets to Vite and changed registration conventions, and Nova 5 continued that drift. Expect to fork and modernize the JS build and Nova::script and Nova::style calls before using it on modern Nova.
- How do I install gijsg/system-resources?
- Installation is via Composer, followed by registering the card in your NovaServiceProvider. Because the package is unmaintained, verify the published version against your Nova major on a staging instance first. In most cases you will vendor the repository into your own namespace rather than relying on the upstream release.
- Is gijsg/system-resources a monitoring or alerting tool?
- No. It is an at-a-glance convenience widget with no persistence layer, no time-series store, no thresholding, and no alerting. If your requirement is operational monitoring, use a maintained solution such as Laravel Pulse instead.
- Can I use gijsg/system-resources without Laravel Nova?
- No, it is a single-purpose Nova card and is inert outside Nova. It provides no API, no events, and no reusable service, so it cannot be used as a general Laravel system-resource reader despite the package blurb. Treat it as a UI artifact rather than infrastructure.
- Does gijsg/system-resources work inside Docker or Kubernetes containers?
- Metric collection typically relies on sys_getloadavg, /proc reads, or shell calls, which behave differently under cgroup v1 versus v2. In locked-down containers these calls can fail silently and render zeros, a failure mode that looks like healthy headroom. Container metrics are per-pod and will mislead for host-level monitoring.
- What are the best alternatives to gijsg/system-resources?
- Laravel Pulse is the preferred alternative: it is first-party, actively maintained, and already ships server-resource cards. Replacing the requirement with Pulse usually eliminates the need for a fork entirely. Only keep this package if you specifically need its exact tile inside an older Nova install.
- Is gijsg/system-resources actively maintained?
- It is effectively unmaintained upstream. The last release was around May 2020, with roughly 29 stars, zero dependents, and no CVE response or compatibility patches. Adopting it transfers the maintenance burden to your team, recurring at every Nova major upgrade.
- Is gijsg/system-resources safe for production use?
- The code surface is small, so the risk is abandonment rather than code quality. There is no community triage, no CVE response, and no compatibility patches. If you adopt it, vendor it into an internal namespace, pin it in a private Composer registry, add CI to catch Nova upgrades, and document that the tile is single-host and non-alerting.
- How do I test gijsg/system-resources before committing to it?
- Run a spike: install the published version against a staging Nova instance and record exactly what breaks. Check your Nova major version, PHP version, Linux versus macOS, cgroup v1 or v2, and whether exec or proc access is available in the runtime. Then estimate the fork effort, usually hours to a day, plus recurring cost per Nova major.