README

Persistant, application-wide settings for Laravel.

Despite the package name, this package works with Laravel 5.x!

Installation

composer require anlutro/l4-settings
Add anlutro\LaravelSettings\ServiceProvider to the array of providers in config/app.php.
Publish the config file by running php artisan config:publish anlutro/l4-settings (Laravel 4.x) or php 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 in config/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.

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.

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 migrate --path=vendor/anlutro/l4-settings/src/migrations (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.

jaapgoorhuis / l4-metatags

Maintainers

Details