Download the PHP package weew/config without Composer

Configuration made simple

Table of contents

• Installation
• Loading configurations
• Accessing configurations
• Configuration formats
• References
• Runtime config
• Environments
  • Setting an environment
  • How it works
  • Adding custom environments
  • Ignoring files
• Extending
  • Custom config drivers
  • Custom environment detector

Installation

composer require weew/config

Loading configurations

The config loader is responsible for loading of the configuration files. All you have to do is to provide a location(file or directory) where it can find your configs. It will scan the locations(s) for configuration files and return you a config object.

Accessing configurations

You can easily access config values by the config key.

Configuration formats

Following formats are supported out of the box.

Plain PHP format example:

INI format example:

YAML format example:

Json format example:

References

You can always reference to other config values from within a config file. To create a reference, simple wrap a config key with curly braces {config.key}`.

You can even reference whole config blocks.

Now when you access the reference value you will get "bar" in return. Keep in mind that references are interpolated at access time (when you call $config->get()). This means that if you change a config value, everyone who references it will receive it's updated value and not the old one.

Runtime config

Sometimes you might want to apply runtime config from an array or similar that also has a higher priority as the config loaded from the filesystem.

Environments

Often you want to split your configurations in multiple files or directories and load them depending on your current environment. This can be achieved trough the environment settings.

Setting an environment

Out of the box it comes with support for dev, test and prod environments. Custom environments can be added on the fly.

How it works

To understand how environments detection works, lets take a look at this directory structure:

In the test environment only the "test" directory and it's contents, "config_test.php" and "config.php" will be loaded. In the prod environment however, it will load only the "prod" directory, "config_prod.php" and "config.php".

Files and folders that have been added to the config loader will be loaded in the order of registration. Inside directories, files are loaded alphabetically.

Adding custom environments

To create your own environments you'll have to register a new rule on the environment detector. The first argument is the name of the environment and the second is an array of masks.

Below is a list of some files and directories that would match the integration environment:

This files will not match:

As delimiter you can use any of this characters: ._+:-.

Ignoring files

This files are ignored by default:

You may specify custom rules to ignore certain files:

Extending

Config loader provides you multiple extension points to alter its behaviour and functionality.

Custom config drivers

Adding your own drivers is very easy. All you have to do is to implement the IConfigDriver interface and pass an instance of the driver to the config loader. You can have multiple active drivers at the same time.

Custom environment detector

You can replace the default environment detector with your own. Just create a new detector which implements the IEnvironmentDetector interface and pass it to the config loader. Also take a look on how to create your own environments.