In this blogpost, my thought was to gather some useful material on how to manage assets on a Symfony project by using the Assetic bundle.

As a project gets bigger, handling more and more assets can become overwhelming. Assetic can help us in organizing where the assets should load, combine multiple assets into a single file, compile assets (e.g. Less or Sass sources into CSS) and even optimize them e.g. by minification.

It is often the case that testing a computer program in the environment in which it was meant to be run not only impactical but outright impossible. This is a common issue in embedded development. BlackMirror aspires to solve the problem for javascript by blackboxing the application, recording the interaction of a successful execution with an API, and asserting that a different program has the same interaction with the API as the first one. A big design goal was for the stored interaction to be serializable so BlackMirror is not only able to replay APIs with a different system state but also APIs that are later not available at all.

This is the first part of our tutorial series on how to configure and deploy a Symfony2 application on Amazon OpsWorks.

At codebender we host our infrastructure under Amazon Web Services and we use Symfony2 for the majority of our web applications. For the application deployment process we use Amazon OpsWorks which is a configuration management service that uses Chef.