Common tools used by Shlink

v4.0.0 2021-10-08 16:28 UTC


Build Status Code Coverage Latest Stable Version License Paypal donate

This library provides some utils and conventions for web apps. It's main purpose is to be used on Shlink project, but any PHP project can take advantage.

Most of the elements it provides require a PSR-11 container, and it's easy to integrate on mezzio applications thanks to the ConfigProvider it includes.


Install this library using composer:

composer require shlinkio/shlink-common

This library is also a mezzio module which provides its own ConfigProvider. Add it to your configuration to get everything automatically set up.


A symfony/cache adapter is registered, under the Psr\Cache\CacheItemPoolInterface service key (as all adapters implement it).

The concrete implementation it returns is different depending on your configuration:

  • An ArrayAdapter instance when the debug config is set to true or when the APUc extension is not installed and the cache.redis config is not defined.
  • An ApcuAdapterinstance when no cache.redis is defined and the APCu extension is installed.
  • A RedisAdapter instance when the cache.redis config is defined.

The last two adapters will use the namespace defined in cache.namespace config entry.



return [

   'debug' => false,

   'cache' => [
       'namespace' => 'my_namespace',
       'redis' => [
           'servers' => [
           'sentinel_service' => 'theservice' // Optional.


Redis support

You can allow caching to be done on a redis instance, redis cluster or redis sentinels, by defining some options under cache.redis config.

  • servers: A list of redis servers. If one is provided, it will be treated as a single instance, and otherwise, a cluster will be assumed.
  • sentinel_service: Lets you enable sentinel mode. When provided, the servers will be treated as sentinel instances.

Doctrine cache support

As other doctrine components still expect a doctrine/cache adapter to be provided, this package still depends on doctrine/cache:^2.0 which just exposes the interfaces and a PSR compatibility layer.

Also, a Doctrine\Common\Cache\Cache service is registered, which is basically an object wrapping the PSR/Symfony cache object registered above.


This module provides a set of useful middlewares, all registered as services in the container:

  • CloseDbConnectionMiddleware:

    Should be an early middleware in the pipeline. It makes use of the EntityManager that ensure the database connection is closed at the end of the request.

    It should be used when serving an app with a non-blocking IO server (like Swoole or ReactPHP), which persist services between requests.

  • IpAddress (from akrabat/ip-address-middleware package):

    Improves detection of the remote IP address.

    The set of headers which are inspected in order to search for the address can be customized using this configuration:

    return [
        'ip_address_resolution' => [
            'headers_to_inspect' => [

Doctrine integration

Some doctrine-related services are provided, that can be customized via configuration:


The EntityManager service can be fetched using names em or Doctrine\ORM\EntityManager.

In any case, it will come decorated so that it is reopened automatically after having been closed.

The EntityManager can be customized using this configuration:



namespace Shlinkio\Shlink\Common;

use Doctrine\ORM\Events;

return [

    'entity_manager' => [
        'orm' => [
            'proxies_dir' => 'data/proxies', // Directory in which proxies will be persisted
            'default_repository_classname' => '', // A FQCN for the class used as repository by default
            'entities_mappings' => [ // List of directories from which entities mappings should be read
                __DIR__ . '/../foo/entities-mappings',
                __DIR__ . '/../bar/entities-mappings',
            'types' => [ // List of custom database types to map
                Doctrine\Type\ChronosDateTimeType::CHRONOS_DATETIME => Doctrine\Type\ChronosDateTimeType::class,
            'load_mappings_using_functional_style' => true, // Makes loader assume mappings return a function which should be invoked. Defaults to false
            'listeners' => [ // Map telling which service listeners to invoke for every ORM event
                Events::postFlush => ['some_service'],
                Events::preUpdate => ['foo', 'bar'],
        'connection' => [ // Database connection params
            'driver' => 'pdo_mysql',
            'host' => 'shlink_db',
            'user' => 'DB_USER',
            'password' => 'DB_PASSWORD',
            'dbname' => 'DB_NAME',
            'charset' => 'utf8',



As well as the EntityManager, there are two Connection objects that can be fetched.

  • Doctrine\DBAL\Connection: Returns the connection used by the EntityManager, as is.
  • Shlinkio\Shlink\Common\Doctrine\NoDbNameConnection: Returns a connection which is the same used by the EntityManager but without setting the database name. Useful to perform operations like creating the database (which would otherwise fail since the database does not exist yet).


A few logger-related commodities are provided by this library.


The LoggerFactory class is capable of creating Monolog\Logger instances based on the configuration described by monolog-cascade, which should be provided under the logger config entry.

This factory can create any logger registered in the configuration, but the service names used must follow the Logger_<name> pattern, where the <name> is the name used under the "loggers" config.

So, given this config:



return [

    'logger' => [
        'formatters' => [
            // ...
        'handlers' => [
            // ...
        'processors' => [
            // ...
        'loggers' => [
            'foo' => [],
            'bar' => [],


You should use the Logger_foo name to get the foo logger, and Logger_bar in order to get the bar one.

Other logger utils

Besides the LoggerFactory, this module provides these utilities:

  • ExceptionWithNewLineProcessor: A monolog processor which captures the {e} pattern inside log messages, and prepends a new line before it, assuming you are going to replace that with an exception trace.
  • LoggerAwareDelegatorFactory: A zend-servicemanager delegator factory that checks if the service returned by previous factory is a Psr\Log\LoggerAwareInterface instance. If it is, it sets the Psr\Log\LoggerInterface service on it (if it was registered).
  • ErrorLogger: A callable which expects a Psr\Log\LoggerInterface to be injected and uses it to log a Throwable when invoked. It will log 5xx errors with error level and 4xx errors with debug level.
  • ErrorHandlerListenerAttachingDelegator: A zend-servicemanager delegator factory that registers all the services configured under error_handler.listeners as listeners for a stratigility ErrorHandler or a ProblemDetailsMiddleware.

HTTP Client

A guzzle HTTP client comes preregistered, under the GuzzleHttp\Client service name, and aliased by httpClient.

It can be customized by adding request and response middlewares using a configuration like this:



use Psr\Http\Message\RequestInterface;
use Psr\Http\Message\ResponseInterface;

return [

    'http_client' => [
        'request_middlewares' => [
            fn (RequestInterface $req): RequestInterface => $req->withHeader('X-Foo', 'bar'),
        'response_middlewares' => [
            fn (ResponseInterface $res): ResponseInterface => $res->withHeader('X-Foo', 'bar'),


Middlewares can be registered as static callbacks with a signature like the one from the example or as service names which resolve to a service with that same signature.


A helper to publish updates on a mercure hub comes preregistered. You need to provide a configuration like this one:



return [

    'mercure' => [

        // A URL publicly available in which the mercure hub can be reached.
        'public_hub_url' => null,

        // Optional. An internal URL in which the mercure hub can be reached. Will fall back to public_hub_url if not provided.
        'internal_hub_url' => null,

        // The JWT secret you provided to the mercure hub as JWT_KEY, so that valid JWTs can be generated.
        'jwt_secret' => null,

        // Optional. The issuer for generated JWTs. Will fall back to "Shlink".
        'jwt_issuer' => 'Shlink',


After that, you can get the publisher from the container, and invoke it to publish updates for specific topics:



use Symfony\Component\Mercure\Publisher;
use Symfony\Component\Mercure\Update;

$publisher = $container->get(Publisher::class);

$publisher(new Update('some_topic', json_encode([
    'foo' => 'bar',

Find more info about the symfony/mercure component here:


  • PagerfantaUtilsTrait: A trait providing methods to get useful info from Pagerfanta\Pagerfanta objects. It requires that you install pagerfanta/core.
  • Paginator: An object extending Pagerfanta, that makes it behave as laminas' Paginator object on regards to be able to set -1 as the max results and get all the results in that case. It requires that you install pagerfanta/core.
  • DateRange: An immutable value object wrapping two Chronos date objects that can be used to represent a time period between two dates.
  • IpAddress: An immutable value object representing an IP address that can be copied into an anonymized instance which removes the last octet.