Weave Code
Laravel Settings Laravel Package
pharaonic/laravel-settings
A Laravel package for managing application settings through a simple, flexible API. Persist configuration values in the database, retrieve them easily at runtime, and organize settings cleanly for small apps or larger projects that need centralized control.
pharaonic/laravel-settings provides a simple, persistent way to manage application settings in Laravel. Store global or grouped key-value settings in the database, retrieve them through an intuitive API, and use caching to keep reads fast. It suits configuration that admins or users need to change at runtime without editing .env or config files.
- Database-backed storage with publishable migrations
- Cached reads for fast access
- Grouped settings for organized configuration
- Helper and API access for reading and updating values
- Laravel-native integration with simple setup
Frequently asked questions about Laravel Settings
- What is pharaonic/laravel-settings used for?
- pharaonic/laravel-settings is a lightweight Laravel package for storing and retrieving settings as key-value configuration. It supports general application settings as well as settings tied to model objects. It also supports database-backed storage and caching.
- How do I install pharaonic/laravel-settings?
- Install it with Composer using composer require pharaonic/laravel-settings. After installation, review the package README for any migration, configuration, or publish steps required by your Laravel version. Laravel package discovery should register the service provider where applicable.
- Can I store settings for a specific model?
- Yes. The package description states that it can store and retrieve settings generally or for model objects. This makes it suitable for per-model configuration alongside global application settings. Check the README for the exact model API.
- Does pharaonic/laravel-settings support caching?
- Yes, the package blurb lists caching as a supported feature. Caching can help avoid repeated database reads when settings are accessed frequently. Review the package documentation for cache configuration and invalidation behavior.
- Is pharaonic/laravel-settings database-backed?
- Yes. The package is described as supporting database-backed settings storage. That means settings are persisted rather than only held in memory or configuration files. You will typically need to run the package migrations before use.
- Can I manage global and grouped settings?
- Yes. It is designed for global settings and grouped settings using key-value configuration. You can use it to manage application-wide options while keeping related settings organized in groups. See the README for the helper names and grouping syntax.
- Which Laravel versions does pharaonic/laravel-settings support?
- The provided context does not specify supported Laravel versions. Check the package composer.json and README on GitHub for the current Laravel and PHP constraints before installing. This is especially important if your application runs an older or newer Laravel release.
- How should I test code that uses Laravel settings?
- Use your normal Laravel test setup and a test database that includes the package migrations. Clear or flush the settings cache between tests if your test cases change cached values. The package context does not list dedicated testing helpers, so verify behavior through its public API.
- Is pharaonic/laravel-settings suitable for production?
- For production use, confirm that your database migrations, cache driver, and deployment process align with the package requirements. Database-backed settings and caching are common production patterns, but cache invalidation should be tested in your environment. Review the repository for maintenance status, releases, and issue activity before adopting it.
- What alternatives should I compare with pharaonic/laravel-settings?
- Compare pharaonic/laravel-settings with other Laravel settings packages such as spatie/laravel-settings, as well as simple config or database key-value approaches. Evaluate schema design, caching behavior, grouped and per-model support, and Laravel version compatibility. The best choice depends on whether you need lightweight helpers or a more structured settings class system.
Weaver
How can I help you explore Laravel packages today?