PHPackages                             howlowck/settings-l4 - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility & Helpers](/categories/utility)
4. /
5. howlowck/settings-l4

ActiveLibrary[Utility & Helpers](/categories/utility)

howlowck/settings-l4
====================

014PHP

Since Jan 8Pushed 12y ago1 watchersCompare

[ Source](https://github.com/howlowck/Settings-L4)[ Packagist](https://packagist.org/packages/howlowck/settings-l4)[ RSS](/packages/howlowck-settings-l4/feed)WikiDiscussions master Synced 3d ago

READMEChangelogDependenciesVersions (1)Used By (0)

Settings Package Laravel
========================

[](#settings-package-laravel)

This package is created to easily change application-level settings that Administator can change.

Setup
-----

[](#setup)

1. Include `"howlowck/settings-l4": "dev-master",` in your application composer.json
2. run `composer update`
3. Add service provider by adding `'Howlowck\SettingsL4\SettingsL4ServiceProvider',` in `app/config/app.php`
4. Add Setting Facade by adding `'Setting' => 'Howlowck\SettingsL4\Facade\Setting'` in `app/config/app.php`
5. Run ` php artisan config:publish howlowck/settings-l4`
6. generate your own migration with the table name 'settings'. (if you want to use a table named other than 'settings', please change the 'table' config item in the configuration file)
7. generate a seed for one row of data. (it's required for settings to work properly)

Configuration
-------------

[](#configuration)

In `app/config/howlowck/settings-l4/config.php`

`table` --- table name

`db` --- whether to use db or redis

`user_column` --- the column name of user if you want to capture who changed the setting (not implemented)

`controller` --- the controller name

`route_path` --- the route path to get to the settings resource controller

`route_before` --- the filter string for before running to the route

`route_after` --- the filter string after running to the route

`form_types` --- the associated array for the input types are is associated with the database data fields, \* is default

To Use
------

[](#to-use)

The Settings Package allows you to interact your settings in various ways.

### Basic Usage

[](#basic-usage)

`Setting::get($settingName)` returns the value of the setting with that name `Setting::set($settingName, $settingValue)` sets the value to the setting name `Setting::all()` returns all the settings in an array

### Built-in views and Routes

[](#built-in-views-and-routes)

1. Include `Setting::route()` in your routes.php this will set up a route group for your settings controller. You can change the path and before/after filters in the config file.
2. Copy the Settings Controller from `vendors/howlowck/settings-l4/src/controllers/SettingsController.php` to your controllers folder. Feel free to change the name of the controller to anything you like, you just have to change the 'controller' configuration item in the config file.
3. Run ` php artisan asset:publish howlowck/settings-l4`
4. Now when you go to any path with `path/to/settings/settingName/edit` you will see a UI that allows you to edit the value.

The available paths are only `path/to/settings` and `path/to/settings/settingName`

### Making your own views

[](#making-your-own-views)

If you prefer to make your own views you can use the following `Setting::getTitle($settingName)` --- gives you the title of the setting

`Setting::getField($settingName)` --- gives you the field of the setting

`Settings::getUpdateUrl($settingName)` --- gives you the correct url to put in your form action property

###  Health Score

20

—

LowBetter than 14% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity6

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity41

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

### Community

Maintainers

![](https://www.gravatar.com/avatar/e08f9bb8228edf1f01ccb4bbccdf8e52ade99b66cbfb538e6df844bdc74a4569?d=identicon)[howlowck](/maintainers/howlowck)

---

Top Contributors

[![howlowck](https://avatars.githubusercontent.com/u/338265?v=4)](https://github.com/howlowck "howlowck (7 commits)")

### Embed Badge

![Health badge](/badges/howlowck-settings-l4/health.svg)

```
[![Health](https://phpackages.com/badges/howlowck-settings-l4/health.svg)](https://phpackages.com/packages/howlowck-settings-l4)
```

###  Alternatives

[beebmx/kirby-env

Enable env variables to Kirby

2037.9k2](/packages/beebmx-kirby-env)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)