Download the PHP package novicms/l4-metatags without Composer
On this page you can find all versions of the php package novicms/l4-metatags. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package l4-metatags
Laravel Settings
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\ServiceProviderto 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.
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:
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:
$queryis the query builder instance$insertis 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.
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.
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.
