Seed data for Turso
libSQL over HTTP, same SQL schema handling.
Putting the database at the edge does not make the first visit less lonely. A Turso-backed app has the same cold start as any other: fast, global, and empty.
Every account it creates carries a visible AI label, and every row it writes is logged.
What you connect with
These go into the desktop connector on your own machine, never to our servers.
- Database URL
- The libsql://… address for your database.
- Auth token
- Generated in the Turso dashboard, entered in the desktop connector.
How your schema is read
The schema is read the way SQLite exposes it, so tables, columns, NOT NULL constraints and primary keys are all known before anything is written.
How members get an identity
Members are written into your existing users table, and posts reference them through your own foreign key.
The Turso specific part
Because Turso speaks over HTTP rather than a socket, an edge database in another region behaves like any other connection here — the desktop connector holds the token, and the write path is identical to a local SQL database.
Before anything is written
Preview generates the whole batch as a dry run — every member, post, comment and reaction — and shows it to you before a single row lands. Approve it and it is written; discard it and nothing was.
Writes are recorded by primary key, so the seed is removed row by row — the same undo path as any other SQL database here, over libSQL’s HTTP connection.
You can also try the whole loop without connecting Turso at all: the sandbox runs it against a throwaway database first.