Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

PHP Laravel 4 Basics Getting Started with Laravel Installing Laravel Homestead

Mohammad Rifqi
PLUS
Mohammad Rifqi
Courses Plus Student 3,218 Points

Laravel error ~/Code

---
ip: "192.168.10.10"
memory: 2048
cpus: 1
provider: virtualbox

authorize: ~/.ssh/id_rsa.pub

keys:
    - ~/.ssh/id_rsa

folders:
    - map: ~/iamuslim1.2/sites
      to: /home/vagrant/sites

sites:
    - map: iamuslim.app
      to: /home/vagrant/sites/lol
      hhvm: true

databases:
    - homestead


# blackfire:
#     - id: foo
#       token: bar
#       client-id: foo
#       client-token: bar

# ports:
#     - send: 50000
#       to: 5000
#     - send: 7777
#       to: 777
#       protocol: udp

Rifqi$ vagrant up Bringing machine 'default' up with 'virtualbox' provider... There are errors in the configuration of this machine. Please fix the following errors and try again:

vm:

  • The host path of the shared folder is missing: ~/Code
Mohammad Rifqi
Mohammad Rifqi
Courses Plus Student 3,218 Points

help pls, i try change folders: map to more detail but not work,

2 Answers

jason chan
jason chan
31,009 Points

Try doing it without VM.

I had the same problem in Laravel 5 and fixed it by bash init.sh.

Run the bash init.sh command from the Homestead directory to create the Homestead.yaml configuration file. The Homestead.yaml file will be placed in the ~/.homestead hidden directory.

If you are changing Homestead.yaml again, you have to re-run bash init.sh again. It will ask for overwriting, say yes.