mirror of
https://github.com/nestriness/nestri.git
synced 2026-09-19 09:15:19 +03:00
46c3a67d4d
Two defects, both found by running it. Neither affects the container path, which is why the images passed: they run the same entrypoints from the repository root, and that turns out to be the load-bearing detail. **The issuer would not start at all.** `apps/auth/tsconfig.json` named React as the JSX runtime — left over from an earlier scaffold; there is no React anywhere in this repository. It only bit when something transpiled from that directory, and then the process died resolving `react/jsx-dev-runtime` from a sign-in screen in `packages/auth` before it bound a port. The package holding those components already said `hono/jsx`, and so did the root; this is the third place agreeing with them. **Neither process could see `.env`.** They ran with the working directory set to their own app, so the environment file the repository documents — the one at the root — was not the one they were offered. The issuer then correctly refused to send a sign-in code rather than logging one, which is the right behaviour and an opaque way to discover a path problem. Both now run from the root, which is also exactly what the images run.
apps/auth
The authentication service for Nestri, built on
@nestri/auth (OpenAuth-style issuer). One
handler, run either as a Cloudflare Worker or as an ordinary HTTP server.
What it does
Hosts the OAuth issuer and the sign-in UI:
- Email code — the only provider, on purpose. Verifying an email address is the one thing that
brings an account into existence, so an account is exactly as recoverable as its email. The
successcallback finds or creates theUserrow, ensures a personal team exists, and issues a JWTusersubject containing{ userID, linkedAccountID }. - Device authorization grant (RFC 8628) — for programs with no browser. A client starts a grant,
a person approves it in a browser, and the client collects tokens by polling. Connecting a Steam
account is not a sign-in and lives in
apps/apiinstead, against a user who already exists.
Key details
- All issuer state is in Postgres. There is no key-value binding. Signing keys, authorization
codes, refresh tokens and device grants each have a table, because each is either a record whose
loss ends every session (the keys) or one with a transition that must happen exactly once while
two callers are touching it — a code is redeemed once, a refresh token is spent once, a grant is
approved once. A store that reads and writes whole records cannot promise that. What is left in
the generic
auth_kvtable is the rate-limit counters, which are allowed to be approximate. - Authorization codes, refresh tokens and device codes are stored as hashes. Each is a bearer credential, so what is kept is enough to recognise one and not enough to present it.
- JWT subjects are defined in
@nestri/core/auth/subjects. - The API verifies tokens against this issuer through
AUTH_ISSUER_URL, which must be this service's public URL: a token carries the address it was minted through and the check is literal.
Structure
src/index.ts # The handler: issuer config, stores, success callback
src/server.ts # The same handler behind a listening socket
src/email.ts # Verification code delivery
wrangler.jsonc # Worker configuration, one environment per stage
Dockerfile # The container, built from the repository root
test/
Running
bun run dev # under the Workers runtime, on :1337
bun run serve # as a plain process, on $PORT (default 1337)
Its only stateful dependency is Postgres — as a HYPERDRIVE binding on Workers, or as
DATABASE_URL anywhere else — alongside the mail settings. Full list and deployment steps:
docs/deploy.md.