Improving Quick-Start guide for Vagrant based setup

[atnanda]

Summary

https://kuma.io/docs/0.5.1/quickstart/universal/ Vagrant 2.2.5 with VirtualBox 5.2.42 on Windows-10, Kuma Version 0.5.1, Universal Mode

Steps To Reproduce

Followed setups listed https://kuma.io/docs/0.5.1/quickstart/universal/ During Vagrant UP, it errors out with at npm setup for "backend" service. This is due to symlink restrictions on Windows (by default on Administrators can create symlink) as documented at https://github.com/npm/npm/issues/9901

Workaround is the do following and re-login or restart windows ::

Right click on Start→Run and launch secpol.msc.

Open Security Settings → Local Policies → User Rights Assignment and select Create symbolic links (that represents SeCreateSymbolicLinkPrivilege). https://i.stack.imgur.com/o8J8x.png )Double-click on the item and add yourself (or the whole Users group) to the list. The changes will apply when you log out and log in again.

Also ssh-ing into individual VMs via Vagrant will leave you with read-only permissions and commands documented in the guide will give you permission errors and will not work. Workaround is to use "sudo" for each kuma shell commands you want to execute against.

Additional Details & Logs

Error: backend: SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) backend: + forever@3.0.0 backend: added 243 packages from 178 contributors in 23.27s backend: npm backend: backend: WARN backend: backend No repository field. backend: npm backend: backend: WARN backend: backend No license field. backend: npm backend: backend: ERR! backend: backend: code backend: EPROTO backend: npm backend: backend: ERR! backend: backend: syscall backend: symlink backend: npm backend: backend: ERR! backend: backend: path backend: ../mime/cli.js backend: npm ERR! dest /home/vagrant/kuma-demo/backend/node_modules/.bin/mime backend: npm ERR! errno -71 backend: npm ERR! EPROTO: protocol error, symlink '../mime/cli.js' -> '/home/vagrant/kuma-demo/backend/node_modules/.bin/mime' backend: npm backend: backend: ERR! backend: A complete log of this run can be found in: backend: npm backend: backend: ERR!

[jakubdyszkiewicz]

CC @devadvocado

[github-actions[bot]]

This issue was inactive for 30 days it will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant please comment on it promptly or attend the next triage meeting.

[github-actions[bot]]

This issue was inactive for 30 days it will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant please comment on it promptly or attend the next triage meeting.

[jakubdyszkiewicz]

We do not support vagrant demo at this moment. Please use a new counter demo https://kuma.io/docs/1.5.x/quickstart/universal/#create-a-data-plane-proxy-for-each-service

[lahabana]

Closing in favour of #145