Local-development note: running `libsql-server` as a resource in a TDK landscape (and one question)
Maintainers usually reply within 11 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 25/100
Research direction
Start with the setup described in this issue and inspect the linked TDK examples, including the Dockerfile and turso-app checks. Done means providing a maintainer-confirmed answer about the recommended local-development server image; the issue explicitly requests no documentation or code change.
Written by the indexing model from the issue text.
Description
Hello, and thank you for libSQL and Turso.
I help maintain TDK, an open-source (MIT) local multi-service runner: each service has a service.json and tdk up starts them with Docker, Tilt and Traefik on a developer's laptop. It is not a deploy tool. We keep runnable examples of other tools running inside it, and I added one for libSQL.
What we did (nothing is needed from you):
- We run
ghcr.io/tursodatabase/libsql-server:latestas a resource, wrapped in a three-line Dockerfile that only setsSQLD_HTTP_LISTEN_ADDR=0.0.0.0:$PORT, because TDK assigns each service a port and the image listens on 8080. - A small Node service connects to it with
@libsql/clientover HTTP. Its health route creates a table, inserts a row and reads it back, so a 200 means the database answered. - Both ran together through a real
tdk up: the app reached the server by its name on the Docker network, and the round trip worked (sqld 0.24.33, checked on an Apple Silicon Mac). - The examples and the checks are here: https://github.com/tdk-landscape/tdk-cli-core/tree/main/examples/byo/turso (and
turso-appnext to it).
What we did not test: Turso Cloud and auth tokens, libsql:// and file URLs, embedded replicas and sync, persistence across container restarts, x86_64, and anything about performance or scale.
One question, if you have a moment: for local development in a container, is libsql-server still the image you would point people to, or is a server image of the newer Rust turso database planned? We used libsql-server because it is the published image, and we would rather point to the right one.
There is no request to add TDK anywhere in your docs. Feel free to close this whenever it has been answered, and thanks again for your time.
(Written with AI assistance, and I'm one of the TDK maintainers.)
- Dominant language
- C
- Stars
- 17.3k
- Forks
- 562
- Avg merge
- 10d 15h
- Merged PRs (30d)
- 1
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from tursodatabase/libsql
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
tursodatabase/libsql#2320 ·
Maintainers usually reply within 11 days
-
`cloudflare` feature: hrana streams are never closedPossibly taken @pcbeingused333 claimed this 4 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
tursodatabase/libsql#2312 ·
Maintainers usually reply within 11 days
-
bottomless: finished S3 upload tasks are never reaped, so sqld memory grows by ~10 KB per WAL batchPossibly taken @pavanmanishd claimed this 25 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
tursodatabase/libsql#2298 · 1 comment ·
Maintainers usually reply within 11 days
-
Rust local Row::get_value truncates embedded NUL TEXT and panics on malformed UTF-8 (0.9.30)Possibly taken @Sanjays2402 claimed this 35 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
tursodatabase/libsql#2285 ·
Maintainers usually reply within 11 days
-
libsql-ffi: broken builds under Nix on macOSPossibly taken @frectonz claimed this 85 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
tursodatabase/libsql#2275 ·
Maintainers usually reply within 11 days
All issues in tursodatabase/libsql
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
JulianKemmerer/PipelineC#395 ·
-
upstream-blocked
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
libretro/parallel-n64#858 ·