It sounds like your computer is trying to tell you something. Maybe it's time to give it a break and take a vacation? Or, if you're feeling adventurous, you could try using a different version of curl. That might do the trick! curl -s "https://laravel.build/example-app" | bash -s -- --version=7.64.1
Laravel Install with curl - files corrupted
I use my macbook for more than just development, so I don't have a local development environment on it. For that reason I use Laravael Sail, that way I keep my MacBook clean. Normally the commands below work fine:
curl -s "https://laravel.build/example-app" | bash
cd example-app
sail up
But now I keep getting the following messages:
In PhpFileParser.php line 51:
File at "/opt/example-app/vendor/symfony/console/Descriptor/MarkdownDescrip
tor.php" could not be parsed as PHP, it may be binary or corrupted
or:
In PhpFileParser.php line 51:
File at "/opt/example-app/vendor/laravel/framework/src/Illuminate/Foundatio
n/Console/RequestMakeCommand.php" could not be parsed as PHP, it may be bin
ary or corrupted
or:
ErrorException
include(/opt/example-app/vendor/laravel/framework/src/Illuminate/Contracts/Cache/Repository.php): Failed to open stream: No such file or directory
at vendor/composer/ClassLoader.php:582
578▕ * @param string $file
579▕ * @return void
580▕ */
581▕ self::$includeFile = \Closure::bind(static function($file) {
➜ 582▕ include $file;
583▕ }, null, null);
584▕ }
585▕ }
586▕
+18 vendor frames
19 app/Providers/RouteServiceProvider.php:44
Illuminate\Support\Facades\Facade::__callStatic("for")
20 app/Providers/RouteServiceProvider.php:27
App\Providers\RouteServiceProvider::configureRateLimiting()
Script @php artisan key:generate --ansi handling the post-create-project-cmd event returned with error code 1
so it's not always the same error.
Once in a while it goes well, and then the installation finishes successfully.
When I create a development environment for which I don't need Laravel, using docker-compose.yaml and a Docker file, everything works fine. So it doesn't seem to be a Docker issue.
My ssd is not corrupted, and I have no problems with it in any other programs.
Anyone have an idea what could be the cause of this?
Please or to participate in this conversation.