title: Laravel 5.3 Homestead Installation on Win 10
body: <p>Following >> <a href="https://laravel.com/docs/5.3/homestead" rel="nofollow">https://laravel.com/docs/5.3/homestead</a></p>
  
  <p>bash init.sh</p>
  
  <pre><code>cp: overwrite '/c/Users/myuser/.homestead/Homestead.yaml'? y
  cp: overwrite '/c/Users/myuser/.homestead/after.sh'?
  cp: overwrite '/c/Users/myuser/.homestead/aliases'?
  Homestead initialized!
  </code></pre>
  
  <p>I don't know if these needs to be overwritten ?</p>
  
  <p>Also ,  I configure homestead.yaml</p>
  
  <p>folders:</p>
  
  <pre><code>  - map: ~/Homestead
        to: /home/vagrant/Code
  </code></pre>
  
  <p>It is showing error[The host path of the shared folder is missing: ~/Homestead]</p>
  
  <p>My homestead installation is 
  $ pwd
  /Homestead</p>
  
  <h1>I am sure some steps are missing can someone help</h1>
  
  <p>Installation method - Per Project Installation</p>
  
  <pre><code>$ vagrant up
  Bringing machine 'default' up with 'virtualbox' provider...
  ==&gt; default: Checking if box 'laravel/homestead' is up to date...
  ==&gt; default: Running provisioner: shell...
  SSH authentication failed! This is typically caused by the public/private
  keypair for the SSH user not being properly set on the guest VM. Please
  verify that the guest VM is setup with the proper public key, and that
  the private key path for Vagrant is setup properly as well.
  </code></pre>
  
  <p>It is a fresh installation !</p>
  
  <p>vagrant destroy &amp;&amp; up</p>
  
  <pre><code>default: Waiting for machine to boot. This may take a few minutes...
      default: SSH address: 127.0.0.1:2222
      default: SSH username: vagrant
      default: SSH auth method: private key
      default: Warning: Remote connection disconnect. Retrying...
      default: Warning: Authentication failure. Retrying...
  Timed out while waiting for the machine to boot. This means that
  Vagrant was unable to communicate with the guest machine within
  the configured ("config.vm.boot_timeout" value) time period.
  
  If you look above, you should be able to see the error(s) that
  Vagrant had when attempting to connect to the machine. These errors
  are usually good hints as to what may be wrong.
  
  If you're using a custom box, make sure that networking is properly
  working and you're able to connect to the machine. It is a common
  problem that networking isn't setup properly in these boxes.
  Verify that authentication configurations are also setup properly,
  as well.
  
  If the box appears to be booting properly, you may want to increase
  the timeout ("config.vm.boot_timeout") value.
  </code></pre>