Vagrant has been successfully used by web developers worldwide for years now. It helps simplifying configuration, unify LAMP configuration per project and avoid sysadmin hurdle in order to configure LAMP stack. Despite these great advantages in team environment however, in my professional career I saw developer who preferred other ways of LAPM or MAMP or WAMP management. That alternative (the old school) setup was causing ongoing issues in team environments that required (lots of) time to resolve. Some developers still have fears of diving into the vagrant, Virtualbox, ansible and related technologies, avoiding it. However the Vagrant box setup is super simple these days – with the beetboxvm. Check out the opensource beetboxvm project on GitHub – it allows single file download and run the `vagrant up` command to get your environment ready out of the box, fast. At the time of writing this article, you only need to download the Vagrant file and place it in your web root. The rest will be configured for you – powerful LAMP, including mail proxy mailhog. The advantages of the beetboxvm project versus other Vagrant boxes You only add config to your project and don’t need to manage a fork of the whole provisioning system. It uses a […]