Weave Code
Settings Laravel Package
escolalms/settings
A flexible settings package for Laravel that stores application configuration as key-value pairs in the database, with caching, typed values, and simple helpers to read and update settings at runtime without editing config files.
General Settings and additional global fields of various types
Frequently asked questions about Settings
- How do I install escolalms/settings in a Laravel application?
- Install it with Composer using composer require escolalms/settings. Laravel package discovery should register the service provider automatically; if not, add the provider manually following the README. After installation, run any published migrations so the settings table exists.
- Does escolalms/settings store settings in the database?
- Yes. The package is described as database-backed key/value settings, so values are persisted in a database table rather than hard-coded in config files. That makes it suitable for runtime-editable application preferences. You will need to run the package migrations to create the storage table.
- How do I read a setting with a default fallback in Laravel?
- Use the package's retrieval API and pass a default value for the case where the key has not been stored yet. This lets application code request a setting without first checking whether it exists. The package explicitly supports default values and fallbacks, so missing keys can resolve to a safe configured value.
- How do I update a setting at runtime without editing config files?
- Call the package's update or save helper with the key and new value. Because settings are stored as database key/value pairs, the change takes effect for subsequent reads without deploying a config change. Use this for admin-editable preferences rather than values that should remain version-controlled in config files.
- Does escolalms/settings support caching?
- Yes, the package blurb mentions caching as part of its settings layer. Caching helps avoid repeated database queries when settings are read frequently. Check the README for cache configuration and how to clear cached values after updates.
- Can I use escolalms/settings for package-level settings?
- Yes. The overview says it is suitable for reusable package-level settings and fits into Laravel's service container and configuration flow. Packages and application code can read and update shared settings through the same API. This avoids each package hard-coding its own configuration values.
- Which Laravel versions are supported by escolalms/settings?
- The provided context does not list exact Laravel version constraints. Check the package's composer.json on Packagist or the repository for the required laravel/framework and PHP versions before installing. For a production application, confirm compatibility with your current Laravel major version first.
- How do I test code that uses escolalms/settings?
- Use a test database and run the package migrations so the settings table is available during tests. In Laravel feature tests, you can update settings through the package API and then assert that your application code reads the expected values. Clear any settings cache between tests if your test suite reuses the same process.
- Is escolalms/settings suitable for production Laravel applications?
- It can be suitable when you need database-backed, runtime-editable settings and understand the migration and caching requirements. Because values live in the database, plan for backups, access control, and cache invalidation after updates. For static configuration that changes only with deployments, Laravel config files remain the simpler choice.
- What are alternatives to escolalms/settings for Laravel settings?
- Common alternatives include spatie/laravel-settings and custom database-backed key/value tables, though exact feature parity varies. Compare caching, typed value support, migration requirements, and Laravel version compatibility before switching. If you only need static configuration, Laravel's built-in config system may be enough.
Weaver
How can I help you explore Laravel packages today?