- What does the Laravel Dashboard Cloudflare stats tile actually do?
- It is a Livewire tile component for spatie/laravel-dashboard that renders Cloudflare zone analytics on an existing dashboard route. The tile displays metrics such as requests, bandwidth, unique visitors, cached versus uncached traffic and threats. It reads cached statistics rather than calling Cloudflare on every page load, so the dashboard stays fast. The package itself is additive and does not add migrations, routes or auth surface.
- Do I need spatie/laravel-dashboard installed to use this tile?
- Yes, this is the hard prerequisite. The tile implements the spatie/laravel-dashboard tile contract and renders through Livewire inside that framework, so it has no standalone value without it. If you are not already running and rendering a dashboard, adopting the whole framework for one Cloudflare card is usually the wrong trade. Confirm the dashboard is live in your stack before spending any engineering time on this package.
- How do I install this Cloudflare tile in a Laravel app?
- Install it with Composer alongside spatie/laravel-dashboard and Livewire, then publish the package config. Create a zone-scoped Cloudflare API token, add the zone ID and token to your env file, register the tile in config/dashboard.php and schedule the fetch command. The integration is small and reversible: config block, scheduler entry, cache namespace and one component.
- What Cloudflare API token permissions does the tile need?
- You should provision a token scoped to Zone Analytics read access on a single zone, with no broader account-level permissions. The tile only reads analytics for the zone you configure, so a least-privilege token is both sufficient and strongly preferred. Avoid account-wide tokens or anything with DNS, firewall or cache purge permissions, since the package has no reason to touch them.
- How does the tile get its Cloudflare statistics, and how often are they refreshed?
- A scheduled fetch command pulls zone statistics from Cloudflare and writes them into cache, and the tile simply renders whatever is cached. Refresh cadence and cache TTL are driven by how you schedule the command and configure the package, so you control the trade-off between freshness and API usage. Make sure the scheduler is actually running in production, otherwise the tile will render stale numbers indefinitely.
- Which Laravel and PHP versions does this package support?
- Check the composer.json constraints before committing, because this is a low-adoption, single-maintainer package and the declared versions may lag current Laravel releases. If the constraint caps below your target version, the fix is typically widening the illuminate/support requirement and running the test suite, which is cheap but should be scoped as work. Treat version drift as a known liability you choose to own, not as something you discover during an incident.
- Does it support multiple Cloudflare zones on one dashboard?
- The typical configuration is one zone per tile instance. If you need several zones side by side, expect to register multiple tiles or write a small subclass or fork for multi-zone support. Budget that effort before treating the package as a roadmap input, since upstream may not accept or prioritise multi-zone changes.
- What happens if the Cloudflare fetch command fails or the API changes?
- That is the realistic failure mode: the tile keeps rendering plausible cached numbers while the scheduled fetch silently fails behind it. Cloudflare analytics schema changes, particularly in the GraphQL API, are the usual source of breakage. Add your own freshness indicator or alerting on the scheduled command so a flat chart cannot mislead you during triage.
- Is this Cloudflare tile safe to run in production?
- The blast radius is genuinely small: no public routes, no migrations, no auth surface and no core overrides, so the worst case is a cheap internal fork. The adoption signal, however, is weak, with few stars, no dependents and a single maintainer. Pin the version, monitor the fetch job and be prepared to patch it yourself under the MIT licence.
- What are the alternatives to this Cloudflare stats tile?
- You can build a small custom tile against the Cloudflare GraphQL Analytics API and reuse your existing dashboard, which avoids depending on an unmaintained package. You can also embed or link out to the Cloudflare dashboard if you only need occasional visibility. If you already run spatie/laravel-dashboard, this package is simply a shortcut; if you do not, a custom tile or the Cloudflare UI is the better call.