- What is kamekun/kame-settings used for in Laravel?
- It provides persistent application settings for Laravel apps, storing key-value configuration in the database instead of flat config files. It is the settings module for the KAME CMS, which is built with Laravel, Livewire, and Tailwind, and it exposes a typed API with caching for reading and updating values. Use it when settings must be editable at runtime and shared across requests.
- How do I install kamekun/kame-settings?
- Install it with Composer using composer require kamekun/kame-settings, then follow the package README for any service provider, config publishing, and migration steps. Because the package is pre-1.0, pin the exact version you have tested rather than using a caret constraint. Run migrations and a smoke test in a non-production app first.
- Which Laravel and PHP versions does kamekun/kame-settings support?
- The provided overview does not state Laravel or PHP version ranges, so check the package composer.json and README before installing. The 0.2.0 refactor may have changed requirements, and no changelog is available in the context. Verify compatibility against your production Laravel major version in a sandbox.
- Does kamekun/kame-settings cache settings values?
- Yes, the package description says it stores, retrieves, and updates settings with caching, which avoids hitting the database on every read. The exact cache store, TTL, and invalidation behavior are not documented in the provided context, so review the source or README. Confirm that updates invalidate cached values in your setup.
- How do I get and set settings with the typed API?
- The package advertises a simple, typed API for retrieving and updating settings, but the specific method names and type behavior are not included in the provided excerpt. Check the README or source for the facade or class surface and expected value types. Write a small smoke test for each getter and setter you plan to use.
- Is kamekun/kame-settings production ready?
- Treat it as pre-1.0 and not yet proven for production critical paths based on the available information. Version 0.2.0 is described only as a refactor test, with no changelog, CI status, or coverage evidence provided. Evaluate it in a throwaway Laravel app and pin the exact version before considering a pilot.
- How do I upgrade from 0.1.x to 0.2.0 of kamekun/kame-settings?
- There is no upgrade guide or changelog in the provided context, and a 0.x minor bump can include breaking changes. Review the diff manually for renamed classes, namespaces, method signatures, config keys, migrations, and serialized data changes. Pin 0.2.0 exactly and test the upgrade in a sandbox before changing production.
- Can I use kamekun/kame-settings outside the KAME CMS?
- It is a Laravel package for persistent key-value settings, so it is presumptively usable in other Laravel applications. However, it is built as the settings module for KAME, which uses Laravel, Livewire, and Tailwind, so check whether it pulls in Livewire or UI dependencies you do not want. Verify package discovery, config publishing, and migrations in your app.
- How do I test kamekun/kame-settings in my Laravel app?
- Run the package own test suite if one is present, then add a smoke test that installs it in a Laravel app matching your production version. Exercise every integration point you need: migrations, reading defaults, writing values, cache invalidation, and typed accessors. The available context does not provide CI status or coverage, so do not rely on upstream tests alone.
- What are alternatives to kamekun/kame-settings for Laravel settings?
- Mature alternatives include spatie/laravel-settings and custom config or database-backed settings implementations, depending on whether you need typed classes, encryption, or multi-tenant support. Compare maintenance activity, Laravel version support, and upgrade guarantees. For a pre-1.0 package like kamekun/kame-settings, evaluate alternatives if you need long-term stability.