-
Notifications
You must be signed in to change notification settings - Fork 238
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
adding libsql driver #291
base: master
Are you sure you want to change the base?
adding libsql driver #291
Conversation
Signed-off-by: Alexis Guerville <[email protected]>
Signed-off-by: Alexis Guerville <[email protected]>
Signed-off-by: Alexis Guerville <[email protected]>
Signed-off-by: Alexis Guerville <[email protected]>
Signed-off-by: Alexis Guerville <[email protected]>
Signed-off-by: Alexis Guerville <[email protected]>
Signed-off-by: Alexis Guerville <[email protected]>
Signed-off-by: Alexis Guerville <[email protected]>
Signed-off-by: Alexis Guerville <[email protected]>
Signed-off-by: Alexis Guerville <[email protected]>
This is blocked by tursodatabase/libsql-client-go#114 |
I just want to follow up on this. There's no where else mentioned libsql and kine/k3s. Libsql have an advantage to use single node first and scale it later if I'm not mistaken and switch to Turso when things get serious. The tursodatabase/libsql-client-go#114 has been merged. |
It was merged but I encountered issues with using actual turso. I could run the cluster with kine when using libsql-sever locally, but when trying with turso the cluster never started. Feel free to pick this back up, but I went another direction for myself. |
libSQL is a fork of SQLite, so I took the SQLite driver code and swapped the actual driver out for the libSQL one.
This allows using Kine with Turso.