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

未关闭
#2,284 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 11 天内回复

还没有人认领这个 Issue。

评估

难度
1/5
预计耗时
1 小时以内
新手友好度
25/100
Issue 类型
文档
描述清晰度
需要澄清
活跃度
活跃
技术栈
docker, node.js, rust
领域
databases, devops

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.)

主要语言
C
星标
17.3k
派生
562
平均合并
10 天 15 小时
30 天内合并 PR
1

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

tursodatabase/libsql 的其他 Issue

查看 tursodatabase/libsql 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。