puter/zopu-code
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
sai/changes
zopu-code/packages/backend/convex/README.md
-Puter e91ca4e6f0 Declare typed Convex env and route auth through @code/env/convex 
- Register SITE_URL, NATIVE_APP_URL, CONVEX_SITE_URL, FLUE_DB_TOKEN in
  convex.config.ts so the generated server.js exposes a typed env object.
- Rewrite auth.ts to consume @code/env/convex and tighten the
  getCurrentUser handler.
- Refresh the backend README to describe the control-plane role and
  generated-file policy.
2026-07-19 17:29:21 +05:30

1.2 KiB
Raw Permalink Blame History

Convex Backend

This directory contains the Convex control plane for the app and daemon runtime. Generated files under _generated/ are maintained by Convex and should not be edited by hand.

Daemon Control Plane

  • schema.ts defines daemon definitions, high-churn daemon presence, leased daemon commands, append-only command events, and the sample todos table.
  • daemons.ts manages stable daemon definitions with upsert, get, and list.
  • daemonRuntime.ts records daemon session lifecycle: connect, heartbeat, disconnect, recordEvent, and bounded event listing.
  • daemonCommands.ts owns the command queue: enqueue, available, claim, start, succeed, fail, cancel, and bounded command listing.

Commands are claimed by daemon session. Preserve the claimedBySessionId ownership checks, leaseExpiresAt expiry semantics, terminal statuses, and bounded query results when changing this flow.

Usage

Convex functions are exposed by file path through the generated api object, for example api.daemonCommands.enqueue or api.daemonRuntime.connect. Run bun run dev:server from the repository root to start the development deployment, and bun run dev:setup when configuring Convex for the first time.