en una máquina virtual Linux (Laravel Homestead), obtengo este error:
PHP Fatal error: Allowed memory size of 1610612736 bytes exhausted (tried to allocate 72 bytes) in phar:///usr/local/bin/composer/src/Composer/DependencyResolver/RuleSetGenerator.php on line 64
Fatal error: Allowed memory size of 1610612736 bytes exhausted (tried to allocate 72 bytes) in phar:///usr/local/bin/composer/src/Composer/DependencyResolver/RuleSetGenerator.php on line 64
Check https://getcomposer.org/doc/articles/troubleshooting.md#memory-limit-errors for more info on how to handle out of memory errors.
Executing the command
in a Laravel Homestead virtual machine with 2 GB of RAM, I can’t finish it because the command stops with the output
When I try to execute the Dusk tests in Laravel Homestead I get the “unknown error: cannot find Chrome binary” error.
I use Laravel Homestead to develop on two machines. I use it because with this solution I have the same development environment in all my machines and in all machines of my coworkers.
Last Tuesday, with the monthly Microsoft update (I suppose), the HTTP responses starts to become very slow, with TTFB (time to the first byte) from 4 to 10 seconds.
If you are using Laravel Homestead and you want to use Laravel Dusk to test your application, you can find some problems.
I was starting Homestead, a Vagrant Virtual Machine and I get this error
Tras actualizar un equipo de trabajo de Windows 7 a Windows 10, Vagrant dejó de funcionar con la máquina Homestead. El error era el siguiente
If you see the message “No input file specified” in the browser (using Homestead as development VM machine), one possible problem is that Homestead doesn’t load the parameters from the config file Homestead.yaml
Try to provision the VM another time, running
$ vagrant reload --provision
If you want to add a new project in Laravel Homestead, you have to edit the “Homestead.yaml” file, adding a new site: