php-di/kernel

Kernel for PHP-DI applications

PHP-DI application kernel

Kernel for building modules with PHP-DI., _(*1)

, _(*2)

Introduction

The Kernel let's you build an application based on PHP-DI modules., _(*3)

Installation

composer require php-di/kernel

Usage

The kernel's role is to create the container. It does so by registering all the configuration files of the modules we ask it to load:, _(*4)

$kernel = new Kernel([
    'twig/twig',
    'doctrine/dbal',
    'vendor/app',
]);

$container = $kernel->createContainer();

If you want to register configuration on the container, you can:, _(*5)

• create a module - this is the recommended solution, read the next sections to learn more

• or set the configuration directly - this is useful in micro-frameworks or micro-applications:, _(*6)

  $kernel = new Kernel();
  $kernel->addConfig([
      'db.host' => 'localhost',
  ]);
  

Installing a module

To install a 3rd party module:, _(*7)

• install the package using Composer

• add it to the list of modules your kernel will load, for example:, _(*8)

  $kernel = new Kernel([
      'twig/twig',
  ]);
  

Creating a module

1. the Composer package name is the module name
2. create a resource directory in your package, usually res/
3. create as many PHP-DI configuration files as needed in res/config/

That's it. Here is what your package should look like:, _(*9)

res/
    config/
        config.php
    ...
src/
    ...
composer.json

When the module is registered in the kernel like this:, _(*10)

$kernel = new Kernel([
    'foo/bar',
]);

all the files in vendor/foo/bar/res/config/*.php will be loaded., _(*11)

Your main application will probably contain configuration files too: it is also a module. Since it may not have a package name in composer.json you will need to set one. You can name it app, for example:, _(*12)

{
    "name": "app",
    "require": {
        // ...
    }
}

That way you can let the kernel load your application as a module:, _(*13)

$kernel = new Kernel([
    'app',
]);

Environments

Applications often need to behave differently according to the environment: dev, prod, etc., _(*14)

PHP-DI's Kernel let you write config for specific environments through a simple convention:, _(*15)

res/
    config/
        config.php
        env/
            dev.php
            prod.php
    ...

You can then instruct the environment to load:, _(*16)

$kernel = new Kernel($modules, 'dev'); // dev environment
$kernel = new Kernel($modules, 'prod'); // prod environment

Note that environments are optional., _(*17)