Silex

Silex is a PHP microframework for PHP. It is built on the shoulders of Symfony and Pimple and also inspired by sinatra.A microframework provides the guts for building simple single-file apps.

Silex exposes an intuitive and concise API that is fun to use. Silex has an extension system based around the Pimple micro service-container that makes it even easier to tie in third party libraries. Silex uses Symfony's HttpKernel which abstracts request and response. This makes it very easy to test apps and the framework itself. It also respects the HTTP specification and encourages its proper use.

Silex is brought to you by Fabien Potencier, the creator of the Symfony framework, and Igor Wiedler. Silex is released under the MIT license. PHP ships with a built-in webserver for development. This server allows you to run silex without any configuration. Silex is not only a framework, it is also a service container. It does this by extending Pimple which provides a very simple service container. Silex defines a range of services: request_stack: Controls the lifecycle of requests, an instance of RequestStack. It gives you access to GET, POST parameters and lots more!routes: The RouteCollection that is used internally. You can add, modify, read routes.

An instance of UrlGenerator, using the RouteCollection that is provided through the routes service. It has a generate method, which takes the route name as an argument, followed by an array of route parameters.controllers: The SilexControllerCollection that is used internally. Check the Internals chapter for more information.dispatcher: The EventDispatcher that is used internally. It is the core of the Symfony system and is used quite a bit by Silex.resolver: The ControllerResolver that is used internally. It takes care of executing the controller with the right arguments.kernel: The HttpKernel that is used internally.

The HttpKernel is the heart of Symfony, it takes a Request as input and returns a Response as output.request_context: The request context is a simplified representation of the request that is used by the router and the URL generator.exception_handler: The Exception handler is the default handler that is used when you don't register one via the error() method or if your handler does not return a Response. Disable it with unset($app['exception_handler']).logger: A LoggerInterface instance. By default, logging is disabled as the value is set to null. To enable logging you can either use the MonologServiceProvider or define your own logger service that conforms to the PSR logger interface.