Fix symlinks in vagrant shared folder on win32 host
Instruct on how to solve Maximum Path Length issue
Merge pull request #2 from mechanica/feature/win32_symlinks

Fix symlinks in vagrant shared folder on win32 host
Set npm loglevel back to http
Mount node_modules folder locally on the guest vm

This would prevent an interference with native modules that were compiled on host (of presumably different architecture) and won't work on guest vm anyway.

It also fixes the problem with npm and windows hosts by elliminating the need in symlinks and working around Maximum Path Length (since modules will never hit the host).
Create temporary folder prior to mounting
Merge pull request #3 from mechanica/feature/npm_http_logs

Set npm loglevel back to http
Merge pull request #4 from mechanica/feature/npm_mountpoint

Mount node_modules folder locally on the guest vm
Add prerequisites for native modules to playbook
Unbuffer Python output for live ansible output

Before that patch, whole stdout of `ansible-playbook` was returned after playbook was completely finished. By unbuffering python output we allow it to appear live in the terminal.

This helps tremendously from the UX standpoint as before that you had to wait for play to finish before you would know the results.
Merge pull request #6 from mechanica/feature/ansible_live_output

Unbuffer Python output for live ansible output
Merge pull request #5 from mechanica/feature/native_modules_prerequisites

Add prerequisites for native modules to playbook
bump :lipstick: