Weave Code
Laravel Simple Setting Laravel Package
elipzis/laravel-simple-setting
A lightweight Laravel package for managing simple application settings as key-value pairs, with helpers to store, retrieve, and update persisted configuration values. Ideal for small dynamic settings without a full CMS.
⚙️ Simple key/value typed settings for your Laravel app with synchronized json export
Frequently asked questions about Laravel Simple Setting
- What is elipzis/laravel-simple-setting used for?
- It is a lightweight Laravel package for managing application settings as persisted key-value pairs. It provides helpers or a facade to store, retrieve, and update typed settings, and it includes synchronized JSON export. It is intended for small dynamic settings such as feature toggles, thresholds, or UI preferences, not for complex configuration management.
- How do I install elipzis/laravel-simple-setting in Laravel?
- For Laravel 11 and PHP 8.2+, require the package with Composer, publish its config and migrations, run the migrations, and then use the provided facade or helper. The evaluation describes the flow as composer require elipZis/laravel-simple-setting, publishing assets, and migrating. Verify the exact publish tags and facade methods in the package README before wiring it into production.
- Does laravel-simple-setting support Laravel 10?
- v1.3.0 targets Laravel 11 and PHP 8.2+, so it is not a drop-in choice for Laravel 10 projects. Teams still on Laravel 10 should either upgrade their framework and PHP runtime or pin to v1.2.0. The evaluation does not indicate that v1.3.0 supports Laravel 10 alongside Laravel 11.
- What Laravel and PHP versions does v1.3.0 require?
- The v1.3.0 release explicitly bumps the package to Laravel 11 and PHP 8.2+. Projects on older Laravel or PHP versions should stay on v1.2.0 unless they upgrade their runtime stack. Confirm your other Composer dependencies also support Laravel 11 and PHP 8.2+ before upgrading.
- How do I store and retrieve settings with this package?
- The package exposes helpers or a facade for storing, retrieving, and updating settings as typed key-value entries. The exact method names and return types are not included in the provided evaluation, so check the README and run a smoke test for read and write operations. Because it persists settings, you should also verify migration and table behavior in staging.
- Does laravel-simple-setting support caching or encryption?
- The provided evaluation does not confirm built-in caching, encryption, or secret management support. Treat it as a simple persisted settings store and add caching or encryption at the application layer if you need those guarantees. Confirm current capabilities in the package documentation before relying on them.
- How do I upgrade from v1.2.0 to v1.3.0?
- First upgrade the application to Laravel 11 and PHP 8.2+ in staging, then bump elipzis/laravel-simple-setting to ^1.3.0. Run any package migrations and smoke-test settings retrieval, updates, and JSON export. The changelog appears to show dependency and CI bumps rather than public API changes, but the evaluation does not confirm backward compatibility, so test before deploying.
- Does this package support multi-tenancy?
- Multi-tenancy is not indicated in the provided evaluation. The package is described as a simple key-value settings store, so tenant-aware scoping, per-tenant encryption, and hierarchical configuration should be treated as out of scope unless the documentation says otherwise. For multi-tenant needs, verify support or use a more specialized configuration package.
- Is laravel-simple-setting a replacement for Laravel config?
- No. Laravel's native config system remains the right place for static, deploy-time configuration. This package is for small dynamic settings that need to be persisted and changed at runtime. It is not positioned as a replacement for complex configuration management, encrypted secrets, or multi-tenant config.
- How is laravel-simple-setting maintained and tested?
- The evaluation describes a small, single-maintainer project with recent Dependabot activity and a recent pull request, suggesting active but limited maintenance. Test coverage and CI status for v1.3.0 are not confirmed in the provided context. For production, review the repository's test matrix and pin a version with a rollback plan.
Weaver
How can I help you explore Laravel packages today?