I have a problem with installing homestead in windows 8, using vagrant.
I typed in like
vagrant box add laravel/homestead as well as
composer require laravel/homestead --dev to make sure that homestead files are installed properly.
also I added environmental variable where homestead.yaml is located.
as a result, I sucessfully access to homestead in cmd.
but when I typed in homestead edit it said,
Windows can not find 'C:\USERS\PETER.homestead\Homestead.yaml' Make
sure you typed the name correctly, and then try again.
so, I checked the file location c:\users\peter.homestead\homestead.yaml, but the directory, .homestead, does not exist in PETER directory.
How can I solve this problem?
Any help or feedback will be appreciated.
Thank you and have a great day.
Do a homestead init for the folder to be generated. Navigate to the path and you should see it.
Related
Looking for some assistance with Vagrant, for what I believe is a Server Variable issue.
I have been trying all weekend to get any kind of Vagrant install up and running. I have followed:
Laravel Homestead installation guide, and
Sitepoint Homestead Vagrant VM guide.
I am using the default folders for install. Whatever I do, after installing Vagrant, I am unable to run 'vagrant up' or vagrant init' because the command 'vagrant' cannot be found (bash: vagrant: command not found). I am trying to execute from the folder with Vagrantfile in it, as suggested by Sitepoint.
I found this Stack Overflow article: Vagrant Command Stopped Working: Command not Found on Windows, but with the current version doesn't work as that bin folder is empty (note that the 'embedded' folder beside it is full, with several 'bin' folders down within the subfolder structure).
I am not familiar enough with Vagrant to know to which folder I should set the server variable, if indeed that is the right answer. It has to be simple, as no sites address this particular issue anywhere. Any assistance will be greatly appreciated.
Win 7, Vagrant 2.1.2, Virtualbox 5.2.14
At the time of writing, Vagrant v2.1.2 is missing vagrant.exe in the i686.msi file.
There are two parts to this answer.
In GitBash, run commands with .\ preceeding the filename(ie .\vagrant up). See earlier comments for the credit for this answer.
Missing executable has been raised as an issue on Github. Without the executable, it, of course, was throwing a command not found error. https://github.com/hashicorp/vagrant/issues/10026?_pjax=%23js-repo-pjax-container
Thanks for your support Rohit.
I have recently started using Laravel Framework 5.6.7 and have everything running smoothly apart from the Zray toolbar it comes with. The toolbar displays the error: "Failed to communicate with Zend Server. See why..."
the link takes me to the troubleshooting page which is of no help:
http://files.zend.com/help/Z-Ray-Azure/Content/troubleshooting.htm
In my local environment I am using the homestead vagrant box:
Vagrant 2.0.2
I tried following this old post but Zray is already installed so I thought it must be a configuration issue:
https://laravel-news.com/installing-zend-z-ray-on-homestead
any ideas on how I can get this toolbar to work would be much appreciated.
I had this issue too and it took a few days to get it resolved. I have no idea if this will work for you but this is how I did it:
Removed all vagrant boxes in my Homestead folder. vagrant box remove --all https://www.vagrantup.com/docs/cli/box.html
Add vagrant box. vagrant box add/laravel/homestead
perform a git pull in the Homestead folder. git pull origin master
went to composer.json and deleted "laravel/homestead": "^7" (also deleted the trailing comma to ensure the JSON was valid).
ran composer update.
Then after a vagrant up --provision (I wasn't sure if provision was needed but I put it just in case), I went to my site and no more Z-RAY issues!
I hope this helps someone else because this was NO fun to figure out.
You have to add
> zray: "true"
in your Homestead.yaml file
I am installing laravel homestead. As I am new on this so maybe i took some steps wrong while installing and setting up laravel homestead on windows.
I followed a tutorial and download laravel homestead box directly and then install it manually by giving it a local disk url. It installed perfectly fine till then. But now when i am trying to "vagrant up" command it says that box doesnt found.
So after that I read somewhere that it we have to add manyual metadata somewhere but I dont know where. And after some changes I am facing this error.
Once you have downloaded the box manually, you need to add it to vagrant config, so vagrant knows about the box for later user. run the following command :
$ vagrant box add --box-version <VERSION_DOWNLOADED> laravel/homestead <path to downloaded file>
After this, make sure to go to the folder where homestead has been cloned (do not do that from the .vagrant directory, just go somewhere else, and avoid path with space, windows generally does not like it; C:\homestead will be just fine for a test) and you can run vagrant up from there
I'm updating Laravel's Homestead to work with the new command line tool and I've hit a hurdle early on.
I've already installed the box and installed the tool by running:
composer global require "laravel/homestead=~2.0"
If I run ~/.composer/vendor/bin/homestead then I get what I'm looking for.
But if I run just homestead on it's own I get:
command not found: homestead
Here's my path:
~/.composer/vendor/bin:/usr/local/heroku/bin:/Users/johndoe/.rvm/gems/ruby-1.9.3-p448/bin:/Users/johndoe/.rvm/gems/ruby-1.9.3-p448#global/bin:/Users/johndoe/.rvm/rubies/ruby-1.9.3-p448/bin:/Users/johndoe/.rvm/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
Where you can clearly see ~/.composer/vendor/bin at the front.
Obviously not the end of the world but just wondering if there's anything I can do?
The ~ character has not been expanded. Add $HOME/.composer/vendor/bin to the path instead.
You need to run this before init.
EPOCLAB:~ Dev$ PATH="~/.composer/vendor/bin:$PATH"
EPOCLAB:~ Dev$ homestead init
There has been a recent change lately when attempting to clone the laravel/homestead package from GitHub. I haven't had trouble in the past trying to add additional virtual machines to my system but now I'm running into a problem.
If you go into GitHub to look at the latest repository for Laravel Homestead you will see that the 'homestead.yaml' file is not in the root directory any longer and has now been replaced by the file 'homestead'.
In the past, I have used the steps below for creating additional virtual machines in my command prompt:
1) Create a new directory (Code2) from within the root directory where VirtualBox and VagrantBox are installed
2) Go into 'cmd' and change to 'Code2' directory
3) Type in 'vagrant box add laravel/homestead --force'
4) Type in 'git clone https://github.com/laravel/homestead.git Homestead_temp'
5) Go into the newly created 'Homestead_temp' directory, copy and paste the files from inside that directory into your 'Code2' root directory.
6) Edit 'src/stubs/homestead.yaml' so that it contains the correct paths for your 'Code2' directory.
7) Go back into 'cmd' and type in 'vagrant up'. When I try to do this, I keep getting a 'read: No such file or directory C:/Users/Jeff/.homestead/Homestead.yaml'
I haven't had trouble in the past adding additional virtual machines but now I am prevented from doing so. Any help is greatly appreciated.
I'm not really sure if this answers my question or not, I'll have to do some research on it but for anybody that is curious about the recent Laravel Homestead changes, check out this article for Laravel 2.0
Hope this information helps!