Weave Code
Laravel Settings Laravel Package
ruangdeveloper/laravel-settings
A lightweight Laravel package for managing application settings stored in the database. Easily get and set configuration values with helper functions, caching support, and a simple API for organizing settings by group or key.
Manage global or model specific setting for your laravel project
Frequently asked questions about Laravel Settings
- How do I install ruangdeveloper/laravel-settings in a Laravel app?
- Install it with composer require ruangdeveloper/laravel-settings, then follow the README to publish any config or migration files and run php artisan migrate. The package is a standard Laravel service provider plus Eloquent stack, so no manual wiring is normally required. Check the version constraint in composer.json against your pinned Laravel major before merging.
- Does laravel-settings support Laravel 10, 11, 12, and 13?
- The current release line includes a v2.3.0 change targeting Laravel 13 compatibility, but the supported range is defined by the illuminate/support constraint in composer.json. Verify that constraint and the CI matrix rather than assuming older majors such as Laravel 10, 11, or 12 are still covered, since a compatibility PR can silently raise the minimum version. Pin the exact package version you have tested.
- How do I get and set settings with the laravel-settings helper functions?
- The package is built around helper functions for reading and writing settings, backed by a database table and a cache layer. The README documents the exact function signatures, so use those rather than guessing at parameter order. If you want an escape hatch, wrap the helpers behind your own small interface.
- Can I organize settings by group or key with laravel-settings?
- Yes, settings can be organized by group or key, which makes it easy to separate application-wide configuration from feature-specific values. Grouping is a convenience layer over a key/value table rather than a separate subsystem. Keep naming conventions consistent so reads stay predictable across the codebase.
- Does laravel-settings cache settings, and how do I clear that cache?
- Caching is part of the package's value proposition, which means writes must invalidate the cached values. Test settings reads after running php artisan config:cache and after any artisan command or queued job that writes settings. If a non-Laravel service also writes to the settings table, you must invalidate the Laravel cache yourself, because the package does not know about external writers.
- Can laravel-settings store model-specific settings per tenant or user?
- The package supports both global and model-specific settings, so per-user or per-tenant preferences fit naturally as long as all readers are Laravel. Model-scoped reads stay inside PHP; if a non-PHP service needs the same values, document the table and cache as a shared contract. Exercise tenant-scoped reads explicitly after any dependency upgrade.
- Does laravel-settings work with config:cache and queued jobs?
- Queue workers can hold stale cached settings, so include reads inside queued jobs in your regression pass. Also verify behavior after config:cache, since settings packages frequently interact badly with cached configuration. Nothing in the v2.3.0 release notes speaks to cache behavior, so treat those paths as untested until you run them.
- How do I run the migrations and publish the config for laravel-settings?
- Follow the README for the publishable config and migration steps; the usual flow is composer require, publish the assets, then php artisan migrate. Confirm the resulting table schema matches what your call sites expect. If you manage the settings table through your own migrations, skip the package's published migration to avoid duplication.
- Is laravel-settings a good alternative to building my own settings table?
- For a single Laravel application, an internal settings table with a cached repository is roughly a day of work and removes a third-party dependency entirely. The package earns its place when you want scoping, caching, and helpers without writing them yourself. If you have only a few call sites, keep the package behind your own interface so replacing it later stays cheap.
- How is laravel-settings maintained, and what happens if it is abandoned?
- The available release evidence is thin: one changelog entry pointing at a single compatibility PR, a modest contributor base, and reliance on one maintainer's continued attention. That pattern is normal for small healthy OSS but justifies a fallback plan. Count how many call sites touch the settings API and keep them behind an interface so abandonment remains a contained problem.
Weaver
How can I help you explore Laravel packages today?