This weekend was kind of special. Both Robert Basic and myself attended the Zagreb PHP user group mini conference, and while this is not the first conference I attended, this was the first one that I did a tech talk on about Vagrant & Puppet(slides are in Serbian).
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.
When working with Symfony 2.3 there is a chance that xdebug will start erroring out with “Maximum function nesting level of ‘100’ reached, aborting!” pretty quick.
Well this was bound to happen sooner or later.
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.
Front end developers in the team we are a part of are using MAMP to serve their websites localy. Aside from that they had virtually no experience setting up vhosts on it. So I thought I should put this little tutorial to help them out a bit.