the schema barrel stops describing a world that ended
three things wrong in one paragraph: it named ecosystem.light.config.cjs, which no longer exists; it called officer-headscale core, which it stopped being on 2026-08-14; and it said installing a plugin 'will have to uncomment its line and push, and building that is still ahead of us', which was built yesterday. now it says what is true — a plugin owns its schema at plugins/<name>/db and install generates the barrel and pushes — and keeps the commented lines for the sidecars still waiting their turn, which is what they are actually for. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
@@ -10,14 +10,16 @@
|
|||||||
//
|
//
|
||||||
// ── Core, and plugins ──
|
// ── Core, and plugins ──
|
||||||
//
|
//
|
||||||
// A fresh install creates the core tables only. Everything under "plugins" is a table belonging to a
|
// A fresh install creates the core tables only. Everything under "plugins" belongs to a sidecar a
|
||||||
// sidecar that a light install does not run — `ecosystem.light.config.cjs` plus `officer-headscale`,
|
// baseline install does not run.
|
||||||
// which is core because the tailnet is the perimeter (see docs/secret-store.md).
|
|
||||||
//
|
//
|
||||||
// The plugin lines are kept, commented, rather than deleted. They are the record of what a table is
|
// A plugin's tables are NOT among them any more: a plugin owns its schema at
|
||||||
// called and which file defines it, and the plugin-install story is going to need exactly that. Nothing
|
// `plugins/<name>/db/schema.ts`, and installing it regenerates `plugin-schemas.gen.ts` (imported at the
|
||||||
// creates them yet: installing a plugin will have to uncomment its line and push, and building that is
|
// bottom of this file) and runs `db:push`. Offscale was the first out, on 2026-08-15.
|
||||||
// still ahead of us.
|
//
|
||||||
|
// The commented lines below are kept rather than deleted. They record what each remaining sidecar's
|
||||||
|
// tables are called and which file defines them — which is exactly what each one needs when its turn to
|
||||||
|
// be extracted comes.
|
||||||
|
|
||||||
// ── Core ─────────────────────────────────────────────────────────────────────────────────────────
|
// ── Core ─────────────────────────────────────────────────────────────────────────────────────────
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user