- What does falbar/nova-card-cache do in a Laravel Nova dashboard?
- It is a Laravel Nova dashboard card that adds a cache reset block so users can clear application cache from the Nova UI. Architecturally it is a thin Nova card plus a service provider over Laravel's existing cache facade. It is intended to make cache clearing convenient from the admin panel, not to introduce a new caching system.
- How do I install falbar/nova-card-cache in a Laravel Nova application?
- Install it with composer require falbar/nova-card-cache, then register the card in NovaServiceProvider::cards(). The overview mentions optional config or asset publishing, but no migrations, queues, or external services. Deploy to a non-production environment first and confirm which cache store the card is allowed to clear.
- Which Laravel and Nova versions does falbar/nova-card-cache support?
- The provided package context does not include an explicit compatibility matrix for Laravel 10, 11, or 12 or for Nova 4 or 5. Nova card APIs have changed across major versions, so treat compatibility as unproven until you check the package metadata and README. Pin your Nova and Laravel versions and run a smoke test before upgrades.
- Does the Nova card enforce authorization before clearing cache?
- The available context does not document whether the card enforces Nova gates or policies or whether visibility is the only control. A cache-clear button visible to the wrong Nova role is an availability risk, so visibility alone is not enough. Wrap the card or its action in a gate such as clearCache and limit it to trusted operators.
- Which cache stores can falbar/nova-card-cache clear, and does it support cache tags?
- The package description does not specify whether it targets only the default store, supports tags, or handles Redis clusters and multi-node file caches correctly. Tagless stores such as file and database behave differently from tagged Redis stores, and a broad clear can wipe unrelated keys. Validate store behavior in your environment and explicitly pin the store the card may clear.
- Will clearing cache from this Nova card affect sessions, queues, or rate limiters?
- If sessions, queues, rate limiters, or other application data share the same cache store, a broad cache clear may affect them. The provided context does not document scoping, selective clearing, or tag handling. Use an isolated cache store or tags where possible, and test side effects before exposing the card broadly.
- Is there an audit trail for who cleared the cache and when?
- The package overview and technical evaluation do not mention audit logging for cache clears. Nova may record some actions depending on your configuration, but the card itself is not documented as providing an audit trail. Add application logging around cache-clearing operations if you need operational or compliance visibility.
- Is falbar/nova-card-cache actively maintained and safe for production?
- The evaluation flags high technical risk relative to value: 1 star, 0 dependents, a single-maintainer namespace, and no documented release cadence or compatibility matrix. That profile suggests a personal utility package rather than a maintained dependency. It can be used in production only after restricting authorization, pinning the cache store, testing your Nova and Laravel versions, and considering an internal fork or wrapper.
- What are alternatives to using a Nova card to clear Laravel cache?
- You can use php artisan cache:clear in a deploy or runbook, build a small custom Nova action with explicit authorization, or expose an internal admin endpoint. Laravel's cache facade and Nova actions are built in and avoid adding an unmaintained dependency. Teams not standardized on Nova get no value from this package.
- How should I test falbar/nova-card-cache before deploying it?
- Install it on a branch, register the card, and test with each cache store your application uses, including Redis and multi-node file caches if applicable. Confirm that a Nova gate blocks unauthorized users and that clearing cache does not break sessions, queues, or rate limits. Add a smoke test to your Nova and Laravel upgrade checklist because compatibility is not documented.