- How do I install laravel-permanent-cache in a Laravel app?
- Install it with Composer using composer require vormkracht10/laravel-permanent-cache. Like most Laravel packages it follows the standard service-provider and facade conventions, so package discovery should register it automatically. Publish any config file the package ships if you need to change defaults, then point your cache configuration at the permanent store. Always check the README for the exact publish tag and store name for your version.
- Does laravel-permanent-cache support Laravel 12?
- Yes, version 0.3.17 adds Laravel 12 support, which is a positive maintenance signal. Before you commit, confirm whether the CI matrix actually runs the test suite against Laravel 12 or whether the illuminate constraint was simply widened. A widened constraint is not the same commitment as a tested target.
- What is the difference between permanent cache and normal Laravel cache?
- A normal Laravel cache entry expires when its TTL elapses. Permanent cache entries never expire on their own and are only removed when you explicitly clear them. That makes the package suitable for settings, configuration values, and expensive queries you want to persist indefinitely.
- How do I clear permanent cache entries?
- Entries are removed only when you explicitly clear them, using the forget-style methods on the permanent cache store or by flushing that store. Check the README for the exact API the package exposes. Because nothing expires automatically, plan a deliberate invalidation strategy for anything that can change.
- Is laravel-permanent-cache safe to use in production at v0.3.x?
- At 0.3.x the package makes no semver guarantee about breaking changes, so a minor bump can rename config keys or change method signatures. Pin the exact version you tested and treat the integration as provisional until v1.0. Run your full test suite with the package installed before rolling it out.
- Which Laravel versions does this package support?
- Laravel 12 support arrives in 0.3.17, but the notes do not publish a full support matrix. Confirm whether Laravel 10 and 11 are still supported or were dropped without notice. If your app is on an older line, this release could become an upgrade blocker rather than an enabler.
- Does it work with Laravel's Cache facade and existing cache API?
- The package is built around a familiar cache API, so you configure it as a cache store and use it much like any other Laravel cache driver. That keeps the learning curve low and lets you swap it in for existing cache calls. Verify the exact store name and configuration keys in the README for your version.
- How should I test laravel-permanent-cache in my application?
- First run your host app's full suite with the package installed but unused, which catches service-provider side effects, container rebinding, and config-cache conflicts. Then spike your primary use case on the exact Laravel version you deploy. Enable one feature behind a config flag and validate in staging before production.
- What are alternatives to laravel-permanent-cache?
- You can use Laravel's built-in rememberForever method, a cache store with a very long TTL, or configuration and database tables for values that rarely change. Those options avoid an extra pre-1.0 dependency. The package's value is a dedicated, convenient permanent store rather than new underlying capability.
- Who maintains laravel-permanent-cache and is it actively maintained?
- It is a subtree split of the Backstage CMS package, so development follows that project. Single-maintainer, bus-factor risk is typical for 0.x packages and should be checked directly on the repository. Review commit cadence, open-issue ratio, changelog quality, and response time on security reports before adopting it.