Menus are simple things, you have a root element, it has children, their children have children, and so on. All nice, clean and simple and utterly dull. Add Knp Menu and bundle to the composer file, run update, go through the docs and set it up, and be on your way. But what happens if you need to construct a menu from different bundles and you have no idea how many items there are and their order.
We upgraded the current project to Symfony 2.3.1 and sent it in production. All was working well for a few days and then interesting bug report came yesterday.
As mentioned here for our current project we are using Vagrant and Puppet. In the link above I described how I solved the pear packages installation under Puppet.
I have been running Vagrant vm with Puppet for the last 4 months for my development work. Most of the vagrant stuff is pretty straight forward, once you grasp the concepts. This post will assume that you are familiar with Vagrant and Puppet, if you are not this is a great place to start. One aspect of my setup was lacking pear packages installation was prone to errors and as a result of that failed dependencies. More often than not I would get this fun little error message