PHPackages                             adrienbrault/silex-bundle - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Framework](/categories/framework)
4. /
5. adrienbrault/silex-bundle

ActiveLibrary[Framework](/categories/framework)

adrienbrault/silex-bundle
=========================

4191[1 issues](https://github.com/adrienbrault/SilexBundle/issues)PHP

Since Aug 1Pushed 11y ago1 watchersCompare

[ Source](https://github.com/adrienbrault/SilexBundle)[ Packagist](https://packagist.org/packages/adrienbrault/silex-bundle)[ RSS](/packages/adrienbrault-silex-bundle/feed)WikiDiscussions master Synced 1mo ago

READMEChangelogDependenciesVersions (1)Used By (0)

SilexBundle
===========

[](#silexbundle)

Integrate Silex into symfony2 full stack (with the exception of pimple/service providers, but we have bundles instead :D).

Motivation
----------

[](#motivation)

My experience of silex is that it's very quick to write a few controllers, and have a website working. However I always end up missing the configuration layer of symfony full stack. I also quickly start to miss the popular symfony bundles.

The idea here is to define your controllers like in a silex application (*fast prototyping*), while keeping the full stack advantages.

For example, you could write an api with the silex api while still being able to leverage the FOSRestBundle features.

Installation
------------

[](#installation)

- Require `adrienbrault/SilexBundle 0.1.*@dev`
- Add `AdrienBrault\SilexBundle\SilexBundle` to your AppKernel
- Add the following to your `routing.yml`:

```
silex:
    resource: .
    type: silex
```

- Configure the bundle to use your "silex files":

```
silex:
    files:
        - "%kernel.root_dir%/../src/controllers.php"
```

- Profit:

```