Homestead "No input file specified" laravel 5

Question

Been trying this for days! I am aware there are other Qs about this, which I have checked over an over. I have one site working and the other not.

I'm using Homestead with Laravel 5 and OSX 10.10.3

I have this .yaml file:

---
ip: "192.168.10.10"

memory: 2048
cpus: 1
provider: virtualbox

authorize: ~/.ssh/id_rsa.pub

keys:
    - ~/.ssh/id_rsa

folders:
    - map: ~/Sites/LaraCode
      to: /home/vagrant/LaraCode

sites:
    - map: myapp.app
      to: /home/vagrant/LaraCode/myapp/public
    - map: newapp.dev
      to: /home/vagrant/LaraCode/newapp/public

databases:
    - homestead

variables:
    - key: APP_ENV
      value: local

Both are Laravel 5 apps in these folders:

/Users/USERNAME/Sites/LaraCode/myapp
/Users/USERNAME/Sites/LaraCode/newapp

myapp.app works fine but newapp.dev gives an error:

No input file specified

in the browser.

I have chmod777 the storage folder. There is an index.php in the public folder. I vagrant provision after changes.

Homestead seems to have been a horrible waste of time.

Answer 1

For me homestead destroy and another homestead up worked. Also I guess you added the new url to you hosts file, correct?

Although I agree that the docs for homestead are a little lacking.

Answer 2

Ok,I finally found an answer for this. I believe I had two homesteads set up, so I had to remove a homestead from the VM

I also had to do update my bash_profile so I could use the homestead commands.

Afterwards, in the homestead folder I ran:

homestead provision

To ensure the yaml file was up-to-date.

All is good now. Both sites are running. Server set-ups are always a nightmare for the less computer techie developers. Where I was caught out was the lack of clear folder guidance on where to execute command lines, hence the conflicting homesteads.