liteas98 / l4-settings
Persistent settings in Laravel.
Requires
- illuminate/cache: ^4.2|^5|^6|^7|^8|^9
- illuminate/support: ^4.2|^5|^6|^7|^8|^9
Requires (Dev)
- laravel/framework: >=5.7
- mockery/mockery: ^1.2
- phpunit/phpunit: ^8.0
Suggests
- illuminate/database: Save settings to a database table.
- illuminate/filesystem: Save settings to a JSON file.
- dev-master
- v1.1.1
- v1.1.0
- v1.0.0
- v0.11.3
- v0.11.2
- v0.11.1
- v0.11.0
- v0.10.0
- v0.9.0
- v0.8.3
- v0.8.2
- v0.8.1
- v0.8.0
- v0.7.3
- 0.7.2
- 0.7.1
- 0.7.0
- 0.6.0
- 0.5.2
- 0.5.1
- 0.5.0
- 0.4.9
- 0.4.8
- 0.4.7
- 0.4.6
- 0.4.5
- 0.4.4
- 0.4.3
- 0.4.2
- 0.4.1
- 0.4.0
- 0.3.0
- 0.2.15
- 0.2.14
- 0.2.13
- 0.2.12
- 0.2.11
- 0.2.10
- 0.2.9
- 0.2.8
- 0.2.7
- 0.2.6
- 0.2.5
- 0.2.4
- 0.2.3
- 0.2.2
- 0.2.1
- 0.2.0
- 0.1.2
- 0.1.1
- 0.1.0
This package is auto-updated.
Last update: 2024-10-20 18:41:55 UTC
README
Persistent, application-wide settings for Laravel.
Despite the package name, this package should work with Laravel 4, 5, 6, 7 and 8 (though some versions are not automatically tested).
Common problems
- Class not found errors: anlutro#38
Installation - Laravel >= 5.5
composer require anlutro/l4-settings
- Publish the config file by running
php artisan vendor:publish --provider="anlutro\LaravelSettings\ServiceProvider" --tag="config"
. The config file will give you control over which storage engine to use as well as some storage-specific settings.
Installation - Laravel < 5.5
composer require anlutro/l4-settings
- Add
anlutro\LaravelSettings\ServiceProvider
to the array of providers inconfig/app.php
. - Publish the config file by running
php artisan config:publish anlutro/l4-settings
(Laravel 4.x) orphp artisan vendor:publish
(Laravel 5.x). The config file will give you control over which storage engine to use as well as some storage-specific settings. - Optional: add
'Setting' => 'anlutro\LaravelSettings\Facade'
to the array of aliases inconfig/app.php
.
Usage
You can either access the setting store via its facade or inject it by type-hinting towards the abstract class anlutro\LaravelSettings\SettingStore
.
<?php Setting::set('foo', 'bar'); Setting::get('foo', 'default value'); Setting::get('nested.element'); Setting::forget('foo'); $settings = Setting::all(); ?>
Call Setting::save()
explicitly to save changes made.
You could also use the setting()
helper:
// Get the store instance setting(); // Get values setting('foo'); setting('foo.bar'); setting('foo', 'default value'); setting()->get('foo'); // Set values setting(['foo' => 'bar']); setting(['foo.bar' => 'baz']); setting()->set('foo', 'bar'); // Method chaining setting(['foo' => 'bar'])->save();
Auto-saving
In Laravel 4.x, the library makes sure to auto-save every time the application shuts down if anything has been changed.
In Laravel 5.x, if you add the middleware anlutro\LaravelSettings\SaveMiddleware
to your middleware
list in app\Http\Kernel.php
, settings will be saved automatically at the end of all HTTP requests, but you'll still need to call Setting::save()
explicitly in console commands, queue workers etc.
Store cache
When reading from the store, you can enable the cache.
You can also configure flushing of the cache when writing and configure time to live.
Reading will come from the store, and then from the cache, this can reduce load on the store.
// Cache usage configurations. 'enableCache' => false, 'forgetCacheByWrite' => true, 'cacheTtl' => 15,
JSON storage
You can modify the path used on run-time using Setting::setPath($path)
.
Database storage
Using Migration File
If you use the database store you need to run php artisan migrate --package=anlutro/l4-settings
(Laravel 4.x) or php artisan vendor:publish --provider="anlutro\LaravelSettings\ServiceProvider" --tag="migrations" && php artisan migrate
(Laravel 5.x) to generate the table.
Example
For example, if you want to store settings for multiple users/clients in the same database you can do so by specifying extra columns:
<?php Setting::setExtraColumns(array( 'user_id' => Auth::user()->id )); ?>
where user_id = x
will now be added to the database query when settings are retrieved, and when new settings are saved, the user_id
will be populated.
If you need more fine-tuned control over which data gets queried, you can use the setConstraint
method which takes a closure with two arguments:
$query
is the query builder instance$insert
is a boolean telling you whether the query is an insert or not. If it is an insert, you usually don't need to do anything to$query
.
<?php Setting::setConstraint(function($query, $insert) { if ($insert) return; $query->where(/* ... */); }); ?>
Custom stores
This package uses the Laravel Manager
class under the hood, so it's easy to add your own custom session store driver if you want to store in some other way. All you need to do is extend the abstract SettingStore
class, implement the abstract methods and call Setting::extend
.
<?php class MyStore extends anlutro\LaravelSettings\SettingStore { // ... } Setting::extend('mystore', function($app) { return $app->make('MyStore'); }); ?>
Contact
Open an issue on GitHub if you have any problems or suggestions.
License
The contents of this repository is released under the MIT license.