- How do I install rudnev/laravel-settings in a Laravel app?
- Install it with Composer using composer require rudnev/laravel-settings. Laravel packages usually register through auto-discovery or a manual service provider entry in config/app.php, so confirm the service provider is registered per its README. After installation, check whether you need to publish and run migrations for the settings table.
- Does rudnev/laravel-settings support Laravel 11?
- The 2.4.0 changelog states that Laravel 11.x support was added. What is not confirmed from that line is whether 11.x was added alongside Laravel 9 and 10 or replaced them. Before adopting, inspect the composer.json constraint and CI matrix to see whether a Laravel 11 application is actually booted in tests.
- How do I define typed settings with laravel-settings?
- The package overview says you define typed settings and then read and write values through a simple API. It does not publish the exact declaration syntax in the provided context, so use the repository README for the concrete API. Expect to declare setting keys with types rather than storing untyped key-value pairs.
- Is laravel-settings cached for performance?
- Yes, the overview says settings are cached for fast access, which matters if you read them frequently during requests. The exact cache store, TTL, and invalidation behavior are not specified in the provided context. Review the package docs to confirm how writes clear or refresh cached values.
- When should I use laravel-settings instead of Laravel config files?
- Laravel config files are static for a deployment and changing them requires a code change and redeploy. laravel-settings is intended for application settings stored in the database that can be edited without code changes, with caching for fast reads. Use it for site-wide configuration that operators need to change; keep infrastructure and secret configuration in environment variables or config files.
- Can laravel-settings store per-user or multi-tenant settings?
- The package description frames it as application and site-wide settings, not per-user preferences. Multi-tenant scoping is not stated in the provided overview, so do not assume row-level tenant isolation exists. If you need per-tenant settings, verify the data model and query scoping in the package before relying on it.
- What Laravel and PHP versions are required by laravel-settings 2.4.0?
- Laravel 11 requires PHP 8.2 or newer, so any package claiming 11.x support has an effective PHP floor at least that high for those applications. The provided context does not include the package's composer.json, so the exact Laravel and PHP constraints for 2.4.0 are unknown. Check composer.json to see whether Laravel 9 and 10 remain supported and whether the PHP requirement was raised.
- How do I test laravel-settings in my Laravel test suite?
- Use a test database and run the package migrations before tests that read or write settings. Clear the cache between tests so cached values from one test do not leak into another. Assert the round trip by writing a setting and reading it back, and follow the package README for any test helpers it provides.
- Is rudnev/laravel-settings actively maintained and safe for production?
- The only verifiable fact in this review context is the 2.4.0 changelog entry adding Laravel 11 support; no dependency manifest, CI matrix, or repository history was supplied. A minor release that adds framework support can reflect real testing or only a widened Composer constraint. For production, inspect recent commits, the CI configuration, and the maintainer's cadence across the last three Laravel majors.
- What are alternatives to rudnev/laravel-settings?
- Other Laravel settings packages, such as spatie/laravel-settings, are commonly evaluated for database-backed typed settings. You can also build a small settings table with your own model, cache layer, and typed casts if you need full control. Compare alternatives on Laravel 11 test coverage, cache invalidation behavior, and maintenance activity.