Local-development note: running `libsql-server` as a resource in a TDK landscape (and one question)

Aperta
#2,284 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 11 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
1/5
Tempo stimato
Meno di un'ora
Idoneità per principianti
25/100
Tipo di issue
Documentazione
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
docker, node.js, rust
Ambito
databases, devops

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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:latest as a resource, wrapped in a three-line Dockerfile that only sets SQLD_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/client over 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-app next 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.)

Lingua principale
C
Stelle
17.3k
Fork
562
Merge medio
10g 15h
PR unite (30g)
1

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di tursodatabase/libsql

Tutte le issue di tursodatabase/libsql

Issue simili

Altre issue su C

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.