Problems with a pulled laravel project

What do you mean with "So he created a new one with ".." --type laravel, and whenever he tries to "vagrant up" he gets an empty folder" ?

When changing configurations in your Homestead.yaml file its likely you need to re-provision your vagrant box. Otherwise I would go and re-install Vagrant globally on your computer. https://laravel.com/docs/5.2/homestead#first-steps

How to deal with domain mapping?

So how do you access your project in homestead via browser? You can do this by mapping a domain name to a given folder in your homestead.yml file. Type the following command: homestead edit. It wil fire you your default editor.

folders:
    - map: ~/Code
      to: /home/vagrant/Code

sites:
    - map: homestead.app
      to: /home/vagrant/Code/Laravel/public
    - map: myproject.dev
      to: /home/vagrant/Code/sandbox/myproject/public

In the folders property I map my local folder to the one in the virtual environment. In the sites property I map it on a project level.

However, simply mapping your project to a domain name like myproject.dev wont be enough. You need to define this in your host file also.

192.168.10.10       myproject.dev

Note that the IP address isnt 127.0.0.1, but 192.168.10.10.