Laravel Settings

Store settings in your Laravel application.

Installation

You can install the package with composer

composer require justijndepover/laravel-settings

After installation you can optionally publish your configuration file

php artisan vendor:publish --tag="laravel-settings-config"

configuration

This is the config file

return [

    /**
     * This setting determines what driver you want to use
     * You can overwrite this driver with your own custom one.
     */
    'driver' => \Justijndepover\Settings\Drivers\Database::class,

    /**
     * Automatically store the app locale
     * If this settings is enabled, the app locale will always be stored in database
     * omitting the need to scope your result set:
     *
     * settings()->forLocale(app()->getLocale())->get('name') becomes: settings()->get('name')
     */
    'auto_store_locale' => false,

    /**
     * Duration the system should cache the fetched database results
     * possible values: 'forever', 'current_request', (int) $seconds
    */
    'cache_time' => 'forever',

];

If you chose the default database driver, you should publish the migration file and execute it

php artisan vendor:publish --tag="laravel-settings-migration"
php artisan migrate

Usage

You have three different ways of interacting with the settings.

Use the global helper function

settings()->get('site_name')

Inject the settings class with dependency injection

use Justijndepover\Settings\Settings;

class HomeController extends Controller
{
    public function __invoke(Settings $settings)
    {
        $settings->get('site_name');
    }
}

Use the global facade

Settings::get('site_name');

all functionality is available with each method.

Examples

// get some value
settings('site_name');

// Is the equivalent of
settings()->get('site_name');

// return a default if no value exists
settings()->get('site_name', 'default');

// store a single value
settings()->set('site_name', 'my-personal-blog');

// store multiple values at once
settings()->set([
    'site_name' => 'my-personal-blog',
    'site_domain' => 'my-personal-blog.com',
]);

// check if a setting exists
settings()->has('site_name');

// delete all settings (both work)
settings()->flush();
settings()->delete();

// delete a single setting (both work)
settings()->forget('site_name');
settings()->delete('site_name');

User settings

In addition to default settings, you can also use this package to store user settings. Add the HasSettings trait to your User model

use Justijndepover\Settings\Concerns\HasSettings; // add this line

class User
{
    use HasSettings; // add this line
}

After installing the trait, you get a settings method on your user

// access user settings throught the model
$user = User::find(1);
$user->settings()->get('preferred_language');

// access user settings through the settings class
settings()->forUser(1)->get('preferred_language');

// all other methods are available as well

Language specific settings

It's possible to store / access settings for specific locales.

settings()->forLocale('en')->set('website', 'my-personal-blog.com/en');

Note on how this works

Caching

Whenever a read operation is executed, the package will check if the value is present in the cache. If it's not found, a read operation will be performed to the database (all values are fetched) and stored in the cache for other calls to consume.

This means that performing multiple reads (even with multiple keys) will only perform one database call.

If a write operation is performed, the cache is cleared. Resulting in a new read from database when a new settings is queried.

IMPORTANT This means the package uses the cache as it's main source, and falls back to the database otherwise. (which is good in most cases) If you change database values directly, you should clear the cache manually.

When working with serverless applications (e.g. AWS Lambda + Bref or Laravel Vapor), this could cause problems if you don't share the cache between the Lambda functions. In this case you should either set your Laravel cache to something like Redis, or disable the cache feature in this package. To do this, publish the configuration file and set the cache_time to 0.

Clearing the cache

It's also possible to clear the cache programmatically:

settings()->clearCache();
// or
Settings::clearCache();

User and locale settings

The default driver always stores a locale and user_id field in the database (defaults to null). Fetching data from the database will also query on these parameters.

To query something different than null, you should chain the forUser or forLocale between the setting and final method.

settings()->forUser(1)->get('name');
settings()->forLocale('nl')->get('name');
settings()->forUser(1)->forLocale('nl')->get('name');

Security

If you find any security related issues, please open an issue or contact me directly at justijndepover@gmail.com.

Contribution

If you wish to make any changes or improvements to the package, feel free to make a pull request.

License

The MIT License (MIT). Please see License File for more information.