WordPress aware key-value config management

dev-master 2018-11-23 11:36 UTC

This package is auto-updated.

Last update: 2021-12-23 23:17:59 UTC


This library is an implementation of the inpsyde/config-interface. It provides uniform configuration management and filtering no matter if the values are provided by environment variables, WordPress database, PHP constants or variables.


$ composer require inpsyde/config


Build the Config object

Create a configuration object from a definition file:

namespace Your\Plugin;

use Inpsyde\Config\Loader;

/* @var \Inpsyde\Config\Config $config */
$config = Loader::loadFromFile(__DIR__.'/config/plugin-config.php');

Build from an array:

namespace Your\Plugin;

use Inpsyde\Config\Loader;
use Inpsyde\Config\Config;

/* @var Config $config */
$config = Loader::loadFromArray( [ /* config definition */ ] );

Configuration schema

The configuration definition follows an associative schema:

string:configKey => array (
    'source' => string
    'source_name' => string
    'default_value' => mixed, optional
    'filter' => int|callable, optional


// config/plugin-config.php

namespace MyPlugin;

use Inpsyde\Config\Source\Source;

return [
    'message.api.endpoint' => [
        // The configuration is read from an environment variable
        'source' => Source::SOURCE_ENV,
        // This is the name of the env variable
        'source_name' => 'SOME_ENV_VARIABLE',
        // Optional: you can provide a default value as fallback if the variable is not set
        'default_value' => 'http://api.tld/endpoint',
        // Optional: If the variable is set, pass it to filter_var() using the following filter argument
        'filter' => FILTER_VALIDATE_URL,
    'domain.some.key' => [
        // In this case the option is read from WP site options
        'source' => Source::SOURCE_WP_SITEOPTION,
        // With this option key
        'source_name' => '_option_key',
        'filter' => FILTER_VALIDATE_FLOAT,
     * You can also provide callables as filter to do
     * more complex filtering
    'domain.some.komplex_value' => [
        'source' => Source::SOURCE_WP_OPTION,
        'source_name' => '_option_key',
        'default_value' => null,
        'filter' => function($value): string {

            return filter_var(

With this declaration in place reading configuration value is done like this:


$apiUrl = $config->get('message.api.endpoint');
$floatValue = $config->get('domain.some.key');
$customFilteredValue = $config->get('domain.some.komplex_value');

Available sources

use Inpsyde\Config\Source\Source;


Defining configuration values on runtime

Sometimes it's useful to define configuration values on runtime (Source::VARIABLE). This is how you can do:

// plugin-config.php

namespace MyPlugin;

use Inpsyde\Config\Source\Source;

return [
    'myPlugin.baseDir' => [
        'source' => Source::VARIABLE,
// my-plugin.php

namespace MyPlugin;

use Inpsyde\Config\Loader;

$container = Loader::loadFromFile(
        'myPlugin.baseDir' => __DIR__


  • Think about namespace support of the keys to split config objects into sub-config that is only aware of a specific namespace. However, the namespace separator should be provided in Inpsyde\Config\Config::NAMESPACE_SEPARATOR
  • Consider allowing callable as default value factory
  • Define a stack of sources for a single key to fall back to another source if the primary one is not defined (e.g. allow a default setting for WordPress multisite that can be overridden for a single site)

Crafted by Inpsyde

The team at Inpsyde is engineering the Web since 2006.


Copyright (c) 2018 David Naber, Inpsyde GmbH

Good news, this plugin is free for everyone! Since it's released under the MIT License you can use it free of charge on your personal or commercial website.


All feedback, bug reports and pull requests are welcome.