Weave Code
Laravel Settings Laravel Package
itmosoft/laravel-settings
itmosoft/laravel-settings provides a simple, developer-friendly way to manage persistent application settings in Laravel. Store configuration values, retrieve them anywhere in your app, and keep runtime behavior easy to customize without editing config files.
Reusable Laravel application settings package with database storage.
Frequently asked questions about Laravel Settings
- What is itmosoft/laravel-settings used for?
- It is a reusable Laravel package for managing persistent application settings backed by the database. Instead of hardcoding values in config files, you store them once and retrieve them anywhere in your application. This makes runtime behavior easy to customize without redeploying configuration changes.
- Does itmosoft/laravel-settings support Laravel 13?
- Yes. The current release widens the framework constraints to accept Laravel 13 alongside Laravel 12. The settings API itself is unchanged, so this is a compatibility maintenance update rather than a feature release. You can adopt Laravel 13 early or stay pinned to Laravel 12.
- How do I install itmosoft/laravel-settings?
- Install it through Composer and register the package following the standard Laravel package shape: service provider registration plus artisan-driven publishing and migration. No additional infrastructure, runtime, or external service is required. Publish the package assets, run the migrations to create the settings storage, then read and write settings through the package API.
- Do I need to change my code when upgrading to version 1.2.0?
- No. The release declares no breaking changes, no deprecations, and no migration steps. The settings API is explicitly unchanged, so consuming code and configuration schemas stay as they are. The upgrade is effectively a version-constraint bump and a dependency resolution.
- What PHP version does itmosoft/laravel-settings require?
- The release notes describe this as a compatibility maintenance update and do not state that the package's own PHP floor was raised. However, Laravel 13 may introduce transitive changes such as a higher minimum PHP version. Check the package's composer.json platform constraints against your production runtime before upgrading.
- Does itmosoft/laravel-settings work with Laravel 11 or earlier?
- No. Laravel 12 is the supported floor for this release. Teams still on Laravel 11 or earlier must complete that framework upgrade first, because this release does not extend support backwards. Plan the framework upgrade before bumping this package.
- How should I upgrade an existing application to this release?
- Confirm the application already runs Laravel 12 or later, then run composer update for this package in a lower environment and verify the lockfile resolves to v1.2.0 without conflicts against other Laravel-ecosystem dependencies. Run your own test suite, paying particular attention to tests that assert on settings reads, writes, caching, or configuration binding. Only then promote the change to production.
- Is itmosoft/laravel-settings well tested enough for production?
- The test suite is thin at roughly 19 tests and 33 assertions, which is about 1.7 assertions per test. That is adequate for proving the framework boots and the API responds, but it is unlikely to cover edge cases such as concurrent writes, cache invalidation, encrypted values, or driver-specific behavior. Treat the CI matrix as proof of compatibility rather than correctness, and add your own integration tests around the settings you depend on.
- Does the package handle caching, encryption, or per-user settings scoping?
- The release notes do not document these behaviors, and the small test suite does not clearly exercise persistence drivers, cache interaction, or multi-tenant scoping. Settings sit between application config, the database, and the cache, so those interactions matter in production. Verify the behavior you need directly against the source or with your own tests before relying on it.
- How does it compare to using Laravel config files or other settings packages?
- Laravel config files are static and require a deploy to change, while this package persists settings in the database so they can be edited at runtime. Other database-backed settings packages exist with similar goals, so compare them on driver support, caching strategy, encryption, and test coverage. If your values rarely change and are safe to version in code, plain config files remain simpler.
Weaver
How can I help you explore Laravel packages today?