I’ve been doing a bit of spring cleaning to the Known repo, removing unnecessary files, tidying up various bits and bobs. One thing I did, because it actually made some client work testing easier, was to move the Known vagrant wrapper into its own repo.
This makes the wrapper much easier to maintain and deploy (for me at least). I also took the liberty of tidying up a number of issues with the ansible configuration which was preventing the provisioning script from working properly.
Next, you need to check out a copy of the Known repo (or your Known based product environment) into a sub directory called
Known. Symlinks should also work.
Run vagrant, and your new Known install will be provisioned as
192.168.33.33, I recommend modifying your
/etc/hosts file to alias this.
Hope you find this useful!
Vagrant logo by Fco.plj – Own work, CC BY-SA 3.0, Link