Laravel Homestead Guide: Setting Up Homestead (2/4)

Official site

Twitter

[christianbalderrama]

> Thank you! You're explanation regarding this matter is crystal clear!

[McprogrammingOrg]

Thank you so much Alex! There was one step I was messing up and you made it so clear for me.

[johnfogarty]

For anyone of windows who is experiencing difficulty you need to install GIT. From there simply launch GIT BASH and you will be able to enter all of the commands above without issue.

[_Wes__]

If you're using Windows and the command 'vagrant up' is taking a really long time, it has most likely thrown an error due to a directory or path name issue. Check the Homestead.yaml file and go to the 'folders:' variable. Check to make sure 'map:' is set correctly.

It needs to be the path to the 'sites' folder from the Homestead.yaml file and may be slightly different to how Alex has shown in this video. For example, Alex's was '~/web/sites, ' however, mine is '~/Documents/www/sites.'

[blueclue]

The tutorial by Alex is good as far as it goes... many comment about not following, not understanding or simply messing up when listening to this. I think it is due to two things - 1) The install example does not consider windows users, and 2) the example jumps over some things that I found are basic or important - maybe there is an assumption that users interested in this topic will be more advanced. Specifically, I would explain the necessity of loading Git, as well as Virtualbox and Vagrant as preparation for Laravel. Then, stress that windows users can use the Git Shell as their terminal browser (instead of windows command prompt). The second is to advise users in windows use Atom as a text editor - not rely upon Notepad. Finally, this brushes too quickly over SSH configuration. As a windows user I am concerned about the hosts file, and want to know what to do about localhost configuration (i.e. 127.0.0.1) when setting up a testing environment. Do I need a private key (SSH) configuration for this? It is not clear to me. After some work on this, I find that my file organization is maybe a bit "dirty" - some of this was installed under my user file (.vagrant_d, .gitconfig, .atom, .homestead) and some under the root file ("web" folder with Homestead subfolder). I think about how to clean this up, and am not certain how to do it. Should I erase and start over??

[JohnOtaalo]

Is it possible you could do one with a windows computer?

[_Wes__]

If 'vagrant up' is failing with some kind of 'permission denied' errors, note that the 'My Documents, ' folder is actually an alias for the 'Documents' folder. They both point to the exact same location, however if you put 'My Documents' in the path name, the command 'vagrant up' will fail. Simply use 'Documents' instead.

Also, when running the 'vagrant up' in command prompt, make sure you've cd'd into the 'Documents' folder instead of the 'My Documents' folder.

For example, my command failed when I ran 'vagrant up' from 'C:\Users\Wes Thorburn\My Documents\www\Homestead' however, it worked perfectly when I ran it from 'C:\Users\Wes (Note the only difference is 'Documents' instead of 'My Documents.')

[kevincooper]

Something is wrong here. He installed homestead in the web folder but then redirects to the home and opens the yaml file?? How is that possible?? The yaml file is supposed to be in the homestead directory inside in the web directory and not home.

[TomBerghuis]

I think it makes more sense to add 192.168.10.10 test.app to /etc/hosts

[MrVengngy]

I installed vagrant in my system, but when I vagrant up it shown different message.

[PaulDessert]

Great video, thanks! Just a quick note for others, you might need to run the bash init.sh command again after you edit the .yaml file. I was getting a "The host path of the shared folder is missing: ~/Code" error. Running the command will resolve the issue. Thanks again for the great video!!

[xev]

I got the no input file specified error..

after changing the yaml file to :
folders:
- map: ~/web/sites
to: /home/vagrant/Code/sites

sites:
- map: test.app
to: /home/vagrant/Code/sites/test

it worked after i did a
vagrant destroy --force
and then vagrant up

[arvinkenndelossantos]

When I tried the test.app:8000 I got a "No input file specified." error.

[jkallend]

didn't work. don't know why. I can not make a connection

[christopherpantelli]

Vagrant is attempting to interface with the UI in a way that requires
a TTY. Most actions in Vagrant that require a TTY have configuration
switches to disable this requirement. Please do that or run Vagrant
with TTY.

Anyway to fix this error. O/S Windows 10

[fuckthis]

I've been doing this for hours and I am stuck. I finally got everything to where I expected it to work and I got "This web page is not available"

I don't know where to go from here please help.

[MrKawior]

"No input file specified" - when I go to test.app:8000. Any solutions? I did everything the same as in this video...

[AA-jndw]

If you already have homestead, do you still need to install laravel and composer?

[blueclue]

Followed the steps on my Windows 10, and got as far as cloning the repository - the command line returned a message that "git" is not recognized as an internal or external command, operable program or batch file. I don't know where to go from here. Vagrant seems to work, but I am stuck at this point.

[KrishneelKumar]

how did you open Homestead.yaml in a text folder, where is the Homestead.yaml file located to open.