- Schema: workspaces (+ workspace_bots, workspace_computers), containers, computers, bot_computers, bots.memory, workspaces.system_prompt, and bots_queue as a bun-sqlite isQueue table - Main computer (and its container record) ensured with the coordinator on signup, seed and /admin/bots; the coordinator's access to it is locked - Effective computer access: direct grants plus workspace computers - Full bot prompt: core instructions, workspace prompts, then memory; bots can rewrite their memory and system prompt - Queue helpers on the native BunSQLite.queue API, plus a handler that heartbeats, serializes per computer, recovers after restarts, reports lost jobs, supports cancelling and pushes outcomes over the WebSocket - Enable SQLite foreign keys at startup so schema cascades fire - Prune finished jobs daily Co-Authored-By: Claude Opus 5.5 <[email protected]>
15 lines
495 B
TypeScript
15 lines
495 B
TypeScript
import BunSQLite from "@moduletrace/bun-sqlite";
|
|
|
|
/**
|
|
* SQLite leaves foreign keys off per connection, so the schema's
|
|
* `ON DELETE CASCADE` rules never fire unless this runs first. bun-sqlite
|
|
* reuses one connection per process, so once at startup is enough.
|
|
*/
|
|
export default async function enableForeignKeys() {
|
|
const res = await BunSQLite.sql({ sql: `PRAGMA foreign_keys = ON` });
|
|
|
|
if (!res.success) {
|
|
throw new Error(`Couldn't enable foreign keys: ${res.msg}`);
|
|
}
|
|
}
|