You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I try to run the migration, but there comes the following error:
cURL error 1: Protocol "libsql" not supported (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for libsql://xxx-yyy.turso.io/v3/pipeline (Connection: turso, SQL: select name from sqlite_master where type = 'table' and name not like 'sqlite_%' order by name)
Do you have any ideas?
Besides that, this Project is so awesome, thank you very much
How to reproduce the bug
run the migration script also with a fresh install of your cms project
Package Version
I dont know
PHP Version
8.3
Laravel Version
11
Which operating systems does with happen with?
No response
Notes
No response
The text was updated successfully, but these errors were encountered:
Hi @wilhelmpa, thanks for submitting the issue . I think I have an idea about what's going on here. The given Turso database URL is defined using the libsql:// protocol. The package doesn't currently recognize the libsql protocol. A quick fix would be to replace the libsql protocol with https.
I know this will be confusing for new users, so I will work on making it unnecessary to replace the protocol in the future.
What happened?
I try to run the migration, but there comes the following error:
cURL error 1: Protocol "libsql" not supported (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for libsql://xxx-yyy.turso.io/v3/pipeline (Connection: turso, SQL: select name from sqlite_master where type = 'table' and name not like 'sqlite_%' order by name)
Do you have any ideas?
Besides that, this Project is so awesome, thank you very much
How to reproduce the bug
run the migration script also with a fresh install of your cms project
Package Version
I dont know
PHP Version
8.3
Laravel Version
11
Which operating systems does with happen with?
No response
Notes
No response
The text was updated successfully, but these errors were encountered: