Homestead: Folder mapping to the wrong document root

I ran into this issue too.

Presumedly, the changes in Homestead.yaml file are being ignored. So, I resolved to refresh it.

! REVISED SOLUTION THAT DOES NOT DESTROY YOUR MACHINE

My solution below is inadequate because it destroys your existing machine. See this solution first!

Once your Homestead environment is provisioned and running, you may want to add additional Nginx sites for your Laravel applications. You can run as many Laravel installations as you wish on a single Homestead environment. There are two ways to do this: First, you may simply add the sites to your Homestead.yaml file and then run vagrant provision.

Alternatively, you may use the serve script that is available on your Homestead environment. To use the serve script, SSH into your Homestead environment and run the following command...

http://laravel.com/docs/homestead#daily-usage

Per the Laravel.io forum the better solution is to run vagrant reload --provision.

See also

*Vagrant Docs

OLD SOLUTIONS: USE AS LAST RESORT

Try these solutions:

1. from ~/Homestead run vagrant reload then vagrant up

or, more drastically

2. from ~/Homestead run vagrant destroy then vagrant up

OPTION 2 DESTROYS YOUR SERVER AND ITS DATABASES

Note: I resorted to step 2.

You can run homestead up --provision to force the reload of the Homestead.yaml file.

If you have a running homestead instance, simply issue the command homestead provision from your local machine.