Weave Code
Laravel Settings Laravel Package
letsgoi/laravel-settings
A Laravel package for managing application settings with database persistence and a simple API for reading, writing, and caching configurable values at runtime. Ideal for editable app configuration without code changes.
At a glance
Frequently asked questions about Laravel Settings
- What is letsgoi/laravel-settings used for?
- It manages application settings that can be edited at runtime and persisted in the database instead of being hard-coded in config files. The package provides a simple API for reading, writing, and caching those values. It fits use cases like admin-editable configuration that should not require a code deploy.
- How do I install letsgoi/laravel-settings?
- Install it with Composer using composer require letsgoi/laravel-settings, then run the package migrations so the settings table exists. Laravel package auto-discovery usually registers the service provider, but check the README for any publish or configuration steps. The provided evidence does not list exact install commands, so confirm them against the repository before deploying.
- How do I read and write a setting at runtime?
- The package advertises a simple API for getting and setting persisted values, but the blurb does not name the exact facade or helper methods. In practice you would call the documented getter and setter from controllers, services, or jobs after installation. Check the repository README for exact method signatures and caching behavior.
- Does letsgoi/laravel-settings cache settings?
- Yes, the package description says it supports caching configurable values at runtime. Caching reduces database reads for settings that are accessed frequently. Review the README to understand cache invalidation when a setting value is updated.
- Which Laravel and PHP versions are supported?
- The provided evidence does not include a supported Laravel or PHP version matrix, so check the package composer.json on Packagist before adopting it. This matters because the 4.0.1 column change relies on Laravel schema capabilities that differ between Laravel 9 and Laravel 10 and newer. Pin a tested version in your composer.json rather than assuming broad compatibility.
- Does letsgoi/laravel-settings own its database table?
- The TPM assessment flags table ownership as unverified: the package persists settings in a database table and ships migrations, but the evidence does not confirm whether that table is package-owned or shared. Before joining or reporting on the value column from application code, confirm ownership. Shared ownership makes future schema changes riskier.
- Is the 4.0.1 migration safe to run in production?
- The 4.0.1 release changes the value column from string to text in a patch release, so treat it as a real schema change rather than a no-op. On MySQL, TEXT columns cannot be indexed without a prefix length, and altering the column type can lock or rebuild the table. Back up the table, test on a production-like copy, and plan a deployment window.
- Can I roll back the 4.0.1 migration?
- Reverting a text column back to a shorter string column is potentially lossy if any stored value now exceeds the old length. The provided evidence does not show whether the migration defines down(), so confirm that before relying on migrate:rollback. If rollback is unsafe for your data, restore from backup instead.
- What are alternatives to letsgoi/laravel-settings?
- Common alternatives include spatie/laravel-settings, a custom Eloquent model backed by cache, or environment and config files for values that do not need runtime editing. Choose based on whether you need database persistence, admin editing, and cache invalidation. Compare Laravel version support and migration behavior before switching packages.
- How actively is letsgoi/laravel-settings maintained?
- The 4.0.1 changelog shows a fix responding to a string-to-text column limitation, which suggests the maintainer addresses production issues. The evidence does not show release cadence or long-term support guarantees. Check recent commits, open issues, and Packagist releases before depending on it.
Weaver
How can I help you explore Laravel packages today?