Laravel Homestead. failed to start "homestead up"

I am trying to start Laravel Homestead. I did it all smoothly through http://laravel.com/docs/4.2/homestead . The last thing I need to do is edit the homestead.yaml file (which I did) and run homestead up

. But every time I try homestead up

I get this output:

/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/shared_helpers.rb:89:in `expand_path': couldn't find HOME environment -- expanding `~' (ArgumentError)
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/shared_helpers.rb:89:in `expand_path'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/shared_helpers.rb:89:in `user_data_path'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/plugin/manager.rb:16:in `user_plugins_file'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/plugin/manager.rb:27:in `instance'
from /Applications/Vagrant/bin/../embedded/gems/gems/vagrant-1.6.5/lib/vagrant/pre-rubygems.rb:22:in `<main>'

      

Does anyone know why this is happening and how to fix it?

note: I am a nob with a terminal, I just started following the laracast tutorials, so my terminal uses Oh-my-zsh and Homebrew, which if possible the zsh or Homebrew syntax would be most helpful.

+3


source to share


2 answers


This answer from the Laracasts forum resolved it for me in Homestead 2.0.8:



.. It turns out that the $ _ENV array is not populated unless you explicitly specify it in php.ini. [...]

To solve this problem, find your_order variable in php.ini and add 'E' to the line, for example: variables_order = "EGPCS".

+6


source


After some research this seems to be a bug in version 2.0.8. The solution is to go back to v2.0.7

First delete your current homestead 2.0.8 folder

rm -rf ~/.composer/vendor/laravel/homestead



Then install Homestead v2.0.7

composer global require laravel/homestead:v2.0.7

+14


source







All Articles