01 June 2016
Associating Vagrant 1.7.2 with an existing VM
Naturally this was a problem because I had made some manual changes to the config that I hadn't had a chance to persist to my puppet config files yet.
To fix the problem I found used the command `VBoxManage list vms` in the directory where my Vagrantfile is. This provided me a list of the machine images it could find.
I then went and edited the file at .vagrant/machines/default/virtualbox/id and replaced the UUID that was in there with the one that the VBoxManage command had output.
Now when I run 'vagrant up' it spins up the correct VM. Happy days.
There are so many different problems that people have with the Doctrine error message: exception 'Doctrine\ORM\ORMInvalidArgument...
Azure Active Directory is a great product and is invaluable in the enterprise space. In this article we'll be setting it up to provide ...
While debugging and setting up Puppet I am still running the agent and master from CLI in --no-daemonize mode. I kept getting an error on...