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
Paul Yorde
10,497 Pointshomestead ymal file is not yeilding a Sites directory?
I am able to vagrant up, and vagrant ssh in the Homestead directory which is this:
/Users/origin/Homestead
However, when I run the vagrant ssh command and look inside the directory, I have a Code directory, not a Sites Directory.
Here is my homestead ymal file:
---
ip: "192.168.10.10"
memory: 2048
cpus: 1
provider: virtualbox
authorize: /Users/origin/.ssh/id_rsa.pub
keys:
- Users/origin/.ssh/id_rsa
folders:
- map: Users/origin/Porjects
to: /home/vagrant/Sites
sites:
- map: laravel.dev
to: /home/vagrant/Sties/mylaravelapp/public
databases:
- homestead
variables:
- key: APP_ENV
value: local
# blackfire:
# - id: foo
# token: bar
# client-id: foo
# client-token: bar
# ports:
# - send: 93000
# to: 9300
# - send: 7777
# to: 777
# protocol: udp
Also the composer command did install laravel into mylaravelapp directory, and when I go to 127.0.0.1:8000, I get a 'no input file speified' error message.
Finally, running vagrant provision after vagrant up doesn't help to see the initial laravel address. Also, changing the directory paths in my ymal file doesn't seem to any affect. For example I continue to get Code as the directory instead of Sites
Paul Yorde
10,497 PointsI do have the Homestead folder in my home directory. In the video, he has:
folders:
- map: Users/hampton/Homestead/Projects
to: /home/vagrant/Sites
What is getting placed into the Projects folder? Isn't that folder in the home directory? So, how is the path going from Homestead/Projects if Projects is outside the Homestead Directory? The Projects folder is what the VM will use for all of our projects, correct?
2 Answers
masterpowers
3,061 PointsWhat OS are you USing? if it is Windows i can help, coz ive been documenting all the step and procedures and done it many times. I can help you out
Paul Yorde
10,497 PointsI am using Yosemite. Also, at some point and time(attempting to reinstall Homestead) a command line option asked if I wanted to overwrite some file. I said yes(00PS), and now nothing is working in regards to Ruby or even Laravel. It seems that file was related to the vagrant or virtual box server system files.
thanks ~
masterpowers
3,061 Pointsi think if this is your original homestead,yaml file folders: - map: Users/origin/Porjects to: /home/vagrant/Sites
sites: - map: laravel.dev to: /home/vagrant/Sties/mylaravelapp/public
then practically you have a TYPO, just correct it,
folders: - map: Users/origin/Projects to: /home/vagrant/Sites
sites: - map: laravel.dev to: /home/vagrant/Sites/mylaravelapp/public
CHECK your ETC host File if laravel.dev is added. if yes.
You need to Serve it at port 8000 , using php artisan serve
Paul Yorde
10,497 PointsI'll give it a shot, thanks.
Jeff Lemay
14,268 PointsJeff Lemay
14,268 PointsI had so much trouble setting this up too. I had the 'No input file specified' error, I think what finally solved everything for me was running 'vagrant provision' after I ran 'vagrant up'.
Regarding the Sites/Code directory, it looks like you're configured to use Code and you should add a Code folder to your homestead folder (assuming you added a homestead folder inside your user directory like it was recommended). It is not required to have a Sites directory but if you wanted one, you'd update your yaml file with /Sites instead of /Code in all locations.