Download the PHP package cubecoding/laravel-settings without Composer

On this page you can find all versions of the php package cubecoding/laravel-settings. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

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 PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • 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.
Please rate this library. Is it a good library?

Informations about the package laravel-settings

Laravel Settings Package

A minimal Laravel package for storing project settings in the database.

Installation

  1. Install the package via Composer:

  2. The package will be automatically registered via Laravel's Package Discovery.

  3. Run the migrations:

Alternatively, you can publish the migrations and then run them:

Configuration

The package comes with a configuration file that you can publish and customize:

This will create a config/settings.php file where you can customize:

Environment Variables

You can also configure the package using environment variables:

Usage

Basic Usage

Advanced Usage

Helper Function

The package provides a convenient global settings() helper function that mimics Laravel's config() helper:

Dot Notation Support

The package supports dot notation for nested settings:

Caching and Performance

The package uses automatic caching for better performance:

Dependency Injection

You can also inject the SettingsManager directly:

Data Types

The package supports automatic type conversion for:

Database Structure

Settings are stored in a settings table:

Column Type Description
id bigint Primary key
key string Unique setting key
value text Setting value
type string Data type (string, integer, float, boolean)
description text Optional description
created_at timestamp Creation date
updated_at timestamp Last update date

API Reference

Settings Facade / SettingsManager

Method Description
get($key = null, $default = null) Get setting (with dot notation). Without key: all settings
set($key, $value = null, $description = null) Set setting (with dot notation and array support)
has($key) Check if setting exists (with dot notation)
forget($key) Delete setting (with dot notation, also deletes children)
all() All settings as nested array structure
getMany(array $keys, $default = null) Get multiple settings (with dot notation)
setMany(array $settings) Set multiple settings
flushCache() Manually clear cache
boot() Load settings from database/cache (automatically called)

Advanced Features

Requirements

Testing

The package uses Orchestra Testbench for development and testing. Orchestra Testbench is a testing framework specifically designed for Laravel packages that provides a minimal Laravel environment for tests.

Why Orchestra Testbench?

Yes, it makes absolute sense to use Orchestra Testbench for development!

Benefits:

Running Tests

Test Structure

Test Types Explained

Unit Tests (tests/Unit/):

Feature Tests (tests/Feature/):

Writing Your Own Tests

Continuous Integration

For CI/CD pipelines (GitHub Actions, GitLab CI, etc.), Orchestra Testbench is ideal because it:

Example GitHub Actions workflow:

License

MIT License


All versions of laravel-settings with dependencies

PHP Build Version
Package Version
Requires php Version ^8.2
illuminate/support Version ^9.0|^10.0|^11.0|^12.0
illuminate/database Version ^9.0|^10.0|^11.0|^12.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package cubecoding/laravel-settings contains the following files

Loading the files please wait ...