Integration with HttpKernelInterface based frameworks.

[defrag]

While this solutions is nice, sometimes i would not like to start another process for stub api. If we extract src/ into TuTu code, we can use stack php url map and make it available in app_test.php for example with Symfony, Laravel etc. This is content from app_test.php which i have run tests from just now. Works fine.

$container = new Pimple\Container();
$container['tutu.root_path'] = realpath(__DIR__ . '/..');
$tutu = new Coduo\TuTu\Kernel($container);

$map = ["/stub/api" => $tutu];

$kernel = new AppKernel('test', true);
$kernel->loadClassCache();
$kernel = (new Stack\Builder())
    ->push('Stack\UrlMap', $map)
    ->resolve($kernel)
;

$request = Request::createFromGlobals();
$response = $kernel->handle($request);
$response->send();
$kernel->terminate($request, $response);

[norberttech]

We can create coduo/tutu-kernel package for that.

[defrag]

Yep, that would be nice. Simple change, but thata would allow nice flexibility.

[norberttech]

Or we can rename this repo into coduo/tutu-standalone and extract src into coduo/tutu

[defrag]

I would say tutu-kernel or tutu-core is fine and lets leave the app as TuTu :)

[norberttech]

I guess this issue can be finally closed thanks to https://github.com/coduo/tutu-core