Hey, thank you for taking your time anyway. I actually got everything working today. It was actually "homestead"'s fault for setting the HOME variable to be in a different location than vagrant expects it to be.
I solved my issue by creating a symlink of the ".vagrant" directory which points to the "~/.homestead/.vagrant". Homestead sets the HOME variable to be "~/.homestead" when using any program, so while the Vagrantfile lies in the composer directory, all the data lies in another directory - hence normal vagrant commands fail. Everything else related to PHPStorm and using XDebug with my machine could be figured out pretty easily with a few hints by others (just googled my problems). I hope this small explanation helps others when they try to google that problem in the future, and I hope that Taylor Otwell reopens the homestead issues page on github so I can report this issue. Cheers! On Thursday, 2 April 2015 23:34:35 UTC+2, Alvaro Miranda Aguilera wrote: > > On Thu, Apr 2, 2015 at 10:08 PM, spaceemotion <[email protected] > <javascript:>> wrote: > > homestead > > Hello, > > I am sorry that I can help any further, but seems are too many layers > with homestead and phpStorm and I am not familiar with those > > perhaps engage homestead/phpstorm ? > > Alvaro > -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
