Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fresh install of Laravel 11 fails during migrate because PHP SqlLite driver is not configured #50959

Closed
MircoBabin opened this issue Apr 8, 2024 · 2 comments · Fixed by laravel/docs#9567
Assignees
Labels

Comments

@MircoBabin
Copy link

Laravel Version

11

PHP Version

8.2.17

Database Driver & Version

No response

Description

The webpage https://laravel.com/docs/11.x/installation mentions:

image

Executing php composer.phar create-project laravel/laravel:^11.0 tripfiles gives the following error:

image

Steps To Reproduce

  • Disable the SqlLite extension in the php.ini
  • Execute php composer.phar create-project laravel/laravel:^11.0 tripfiles

A pre-install step is missing. This should check the Php requirements like minimum Php version and required Php extensions (SqlLite, ...) before installing. And abort the installation if requirements fail.

@driesvints driesvints self-assigned this Apr 8, 2024
@driesvints driesvints added the bug label Apr 8, 2024
@nunomaduro
Copy link
Member

Can you try php composer.phar create-project laravel/laravel tripfiles? That should address the issue, as the --graceful flag was added on the migrate command. You probably on Windows, so using ^11.0 will make you use Laravel 11.0.0 that does not have yet the --graceful flag.

Meanwhile, made a PR on the docs to remove the ^11.0 (caret), that is not supported on Windows:

@MircoBabin
Copy link
Author

I'm indeed on Windows. I can confirm that php composer.phar create-project laravel/laravel tripfiles installs correctly.

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants