weidacat/cascading-config

Bringing the cascading configuration system back to Laravel 5.

2.0.0 2015-11-16 17:01 UTC

This package is not auto-updated.

Last update: 2024-04-10 22:14:05 UTC


README

Build Status Dependency Status License

A simple package that brings the cascading configuration system back into Laravel 5.

Requirements

  • Laravel 5

Features

  • Laravel-4 style cascading config (can't believe I'm writing this)
  • Nested configuration is fully supported

Installation

First, require weidacat/cascading-config into your composer.json and run composer update:

composer require "weidacat/cascading-config:dev-master"

An environment-based configuration directory should have a name with this format config/{APP_ENV}, and reside in the same directory as the default config dir. For Laravel, php artisan vendor:publish will create a sample directory for your local environment.

Your application structure now should have something like this:

config
├── app.php
├── auth.php
├── cache.php
├── compile.php
├── database.php
├── mail.php
└── local
    ├── app.php
    ├── auth.php
    ├── cache.php
    ├── mail.php
    └── nested
    └── app.php

Fill the configuration into your environment-based config directory (config.local, config.staging, config.production), just like what you've always done in Laravel 4,

Usage

For Laravel

  1. Add the package's service provider class into config/app.php:

    'providers' => [
        /*
         * ...
         */
        App\Providers\AppServiceProvider::class,
        App\Providers\EventServiceProvider::class,
        App\Providers\RouteServiceProvider::class,
    
        Weidacat\CascadingConfig\CascadingConfigServiceProvider::class,
    ],

Notes

Because of the way array_merge_recursive() works, a config key with value being an indexed (non-associative) array (for instance, app.providers) will have the value's items overridden. See #6 for more details on this behavior, and how to work around it.

License

MIT © Phan An