configurators is a list of ApplicationConfigurator implementations which, in the same order as defined in the list, can add routes and middlewares to the instance of Slim\App.

Once you have configured the bridge, you can create a simple index.php script in your document root, using nette/bootstrap to build the container:

<?php// include Composer autoloaderrequire_once__DIR__.'/path/to/vendor/autoload.php';// configure and create the DI container$configurator=newNette\Configurator();$configurator->setTempDirectory(__DIR__.'/path/to/temp');$configurator->addConfig(__DIR__.'/path/to/config.neon');$container=$configurator->createContainer();// run the configured Slim application$container->getByType(Slim\App::class)->run();

Don't forget to configure your web server to pass the incoming requests to the index.php script.

The Controller is automatically fetched from the DI container as long as it is registered as a service. This way you can optimize your applications because dependencies are not instantiated unnecessarily.

If you don't use invokable classes and want to point to a specific method of the class, you can write

After some time in production, I think this package is ready for a stable release. This release includes a fix in the internals which prevents conflicts between unprefixed services in the DI container, see #1. As a result, SlimNetteBridge uses its own implementation of the PSR-11 container interface, and therefore providing such implementation from your code is no longer necessary.