I'm unable to run "homestead up"

I just updated Laravel Homestead and I am encountering the same problem. I haven't found anything beneficial on the web yet. I'll keep troubleshooting and let you know if I find a solution. It definitely is irritating!

Link to your SO if it gets answered :P http://stackoverflow.com/questions/27285627/laravel-homestead-unable-to-run-homestead-up

Another maybe? http://stackoverflow.com/questions/27288947/couldnt-find-home-environment-expanding

Yep, experiencing the exact same issue since the upgrade a few minutes ago.

Try setting a HOME path temporarily

export HOME=/Users/name/

I'm not sure what it's meant to be but it could be home of the homestead box

Already tried that, but unfortunately no luck. I've tried to set it in my .zshrc file (I'm using Oh My Zsh). Thanks for the effort though, greatly appreciated.

Remember, you can directly input export into the CLI and it will be set for that session. No need to put it into your rc file just for testing (which would also need a shell restart).

Same problem here. I change the HOME path, it didn't fix it.

It's this part which it can't find (from the file it's erroring on)

# This returns the path to the ~/.vagrant.d folder where Vagrant's
# per-user state is stored.
#
# @return [Pathname]
def self.user_data_path
  # Use user spcified env var if available
  path = ENV["VAGRANT_HOME"]

  # On Windows, we default to the USERPROFILE directory if it
  # is available. This is more compatible with Cygwin and sharing
  # the home directory across shells.
  if !path && ENV["USERPROFILE"]
    path = "#{ENV["USERPROFILE"]}/.vagrant.d"
  end

  # Fallback to the default
  path ||= "~/.vagrant.d"

  Pathname.new(path).expand_path
end

Add me to this list. 167135bba done goofed.

Similar issue here. After updating to homestead 2.0.8, "homestead" command seems to be broken... "vagrant is not recognized as an internal or external command"

http://new.tinygrab.com/db0e29f6dc56347d076cb1d8690d9c061b519e7ec2.png

This is in error introduced in version 2.0.8. Its possible to revert back to an older version.

First delete the current homestead folder

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

Then install version 2.0.7

composer global require laravel/homestead:v2.0.7

This worked fine for me at least.

Yeah looks like Vagrant doesn't get the right data with this commit: https://github.com/laravel/homestead/commit/167135bbac3966be7ac05446c7da0d8bee50c34e

Vagrant tries to find the VAGRANT_HOME or something from the $_ENV array. Maybe there's a new setting in yaml file needed.

Edited the up command to var_dump $_ENV and this is all that gets passed

homestead up
array(1) {
  ["VAGRANT_DOTFILE_PATH"]=>
  string(21) "~/.homestead/.vagrant"
}

Because I don't want to deal with Homestead horrible v2 (first PHP composer based CLI, now this, one VM per user, etc), I create a simple fork to use it like any Vagrant box: https://github.com/zoontek/purestead

I know it's far from a solution, but I do the job.

Try this https://github.com/fideloper/Vaprobash

I stay away from Homestead too, Vaprobash has everything and you can customise it yourself. Multiple VMs, multiple sites, it's all in one file.

More info: http://fideloper.github.io/Vaprobash/

So I fixed the issue on my machine. Turns out that the $_ENV array isn't populated unless you explicitly state it in the php.ini. The commit that Taylor made to Laravel Homestead works to pass the $_ENV variable, it's just that it's empty by default.

To solve it, find the variables_order in your php.ini and add 'E' to the string, like so: variables_order = "EGPCS".

Least there's a non PHP way now. Need PHP to install a VM :P

Thank you all for your input!! I tried vinkla's way of reverting back to v2.0.7 and it worked perfectly.

If you want to use the latest, follow the last reply on the first page. 2.0.7 works though :)

The solution @ELD provides works, but now a new issue raises:

A VirtualBox machine with the name 'homestead' already exists.
Please use another name or delete the machine with the existing
name, and try again.

That's a local issue. Delete the files fully and re-install it.

Laravel and Homestead is fairly new to me. How do I find my php.ini? to do this:

"To solve it, find the variables_order in your php.ini and add 'E' to the string, like so: variables_order = "EGPCS"."

Thanks,

@bashy: fixed that as well, everything is working fine now. Thanks.

@dstudio101 Try this

@dstudio101 another way to find it is to run this command in your CLI:

php -i | grep "Loaded Configuration"

As long as you're in a bash terminal, it'll work fine.

@floristenhove @ELD

Where do I place this page file? and how will I access this page?

As I understand, "homestead up" will make the homestead laravel guest machine run -- which I can't and then I can more or less work with the apps with the guest machine.

I can't make homestead up work for the same reason as the first post here.

Forgive me, I am disoriented. I do have a local php running in my desktop if that's what the post mean and not the one that is run via homestead... let me try.

The way @ELD suggests is way better than my link. Run the command he provides in your local machine's terminal. You need your local php to run the homestead CLI tool. Alternatively you could also clone the git repository yourself and use Homestead without the CLI tool. For more information on this please take a look at the docs.

Editing the php.ini made it for me, thanks !

Btw, an even simplier command to find where is the php.ini file :

php --ini

and on Linux systems HOME path is /home/yourusername instead of /Users/yourusername

@UnSeulT good to know. I didn't even know about that command. That is even easier. No need to pipe to grep. And yes, a subtle but aggravating difference between true Linux systems and Macs. Nothing that didn't take a little getting used to, but still irritating.

Thanks,

setting variables_order = "EGPCS" just worked.

i was looking for a solution for 2 hours.

@bashy Least there's a non PHP way now. Need PHP to install a VM :P

Need PHP on host machine to install a VM to run PHP so that you don't have to have PHP on your host machine.

FTFY.

If you downgrade or move version the homestead version, FYI you will lose your .vagrant files / ability to use vagrant up . So you will need to open virtualbox to start the machine and salvage any mysql databases needed.

Heres a patch to get it working again

Open ~/.composer/vendor/laravel/homestead/homestead

Add
$_ENV['HOME'] = getenv('HOME');

After
$_ENV['VAGRANT_DOTFILE_PATH'] = '~/.homestead/.vagrant';