Added missing newline to .gitignore
Added .gitignore rules for Symfony2 files and folders
Replaced existing Silex application with initial Symfony2 application structure

As generated by `composer create-project symfony/framework-standard-edition ./soundvenirs-backend 2.5.*`
Re-adding cache bootstrap file
Created Soundvenirs\ApiBundle

As generated by:

    $ php bin/console generate:bundle --namespace=Soundvenirs/ApiBundle --format=yml

      Welcome to the Symfony2 bundle generator

    In your code, a bundle is often referenced by its name. It can be the
    concatenation of all namespace parts but it's really up to you to come
    up with a unique name (a good practice is to start with the vendor name).
    Based on the namespace, we suggest SoundvenirsApiBundle.

    Bundle name [SoundvenirsApiBundle]:

    The bundle can be generated anywhere. The suggested default directory uses
    the standard conventions.

    Target directory [/Users/manuel.kiessling/Dropbox/Projects/soundvenirs-backend/src]:

    To help you get started faster, the command can generate some
    code snippets for you.

    Do you want to generate the whole directory structure [no]? yes

      Summary before generation

    You are going to generate a "Soundvenirs\ApiBundle\SoundvenirsApiBundle" bundle
    in "/Users/manuel.kiessling/Dropbox/Projects/soundvenirs-backend/src/" using the "yml" format.

    Do you confirm generation [yes]? yes

      Bundle generation

    Generating the bundle code: OK
    Checking that the bundle is autoloaded: OK
    Confirm automatic update of your Kernel [yes]? yes
    Enabling the bundle inside the Kernel: OK
    Confirm automatic update of the Routing [yes]? yes
    Importing the bundle routing resource: OK

      You can now start using the generated code!
Removed unneccessary boiler plate bundle files
Created Soundvenirs\SoundBundle

As generated by:

    $ php bin/console generate:bundle --namespace=Soundvenirs/SoundBundle --format=yml

      Welcome to the Symfony2 bundle generator

    In your code, a bundle is often referenced by its name. It can be the
    concatenation of all namespace parts but it's really up to you to come
    up with a unique name (a good practice is to start with the vendor name).
    Based on the namespace, we suggest SoundvenirsSoundBundle.

    Bundle name [SoundvenirsSoundBundle]:

    The bundle can be generated anywhere. The suggested default directory uses
    the standard conventions.

    Target directory [/Users/manuel.kiessling/Dropbox/Projects/soundvenirs-backend/src]:

    To help you get started faster, the command can generate some
    code snippets for you.

    Do you want to generate the whole directory structure [no]? no

      Summary before generation

    You are going to generate a "Soundvenirs\SoundBundle\SoundvenirsSoundBundle" bundle
    in "/Users/manuel.kiessling/Dropbox/Projects/soundvenirs-backend/src/" using the "yml" format.

    Do you confirm generation [yes]? yes

      Bundle generation

    Generating the bundle code: OK
    Checking that the bundle is autoloaded: OK
    Confirm automatic update of your Kernel [yes]?
    Enabling the bundle inside the Kernel: OK
    Confirm automatic update of the Routing [yes]?
    Importing the bundle routing resource: OK
SoundBundle doesn't need routing
Removed unneeded files from SoundBundle
Removed another unneeded file from the SoundBundle
Added Sound entity
Added Doctrine ORM mappings to Sound entity
Added Doctrine migrations dependency
Added missing sqlite database config setting
Registered Doctrine Migrations Bundle
Added migration for Sound table creation
Removed ApiBundle DefaultController and test
Added test case for GET /api/sounds/:id
Test case for GET /api/sounds/:id is green
Renamed test case for retrieving one sound via API