logaritmisk/biggus-dickus
1
0
Fork 0
Code Issues 17 Pull Requests Actions Packages Projects Releases Wiki Activity

Wire the Spectrum cataloguing seed into runtime #14

New Issue
Closed
opened 2026-06-02 09:28:04 +00:00 by logaritmisk · 1 comment
logaritmisk commented 2026-06-02 09:28:04 +00:00
Owner
Copy Link
Copy Source

db::seed::seed_spectrum_cataloguing exists and is idempotent, but nothing invokes it yet. Decide how/when an org's baseline field set gets seeded:

  • a server --seed / config flag that runs it on startup, and/or
  • a small CLI subcommand, and/or
  • part of per-org provisioning (the control plane), so a freshly-provisioned org gets the baseline Spectrum fields automatically.

Likely the provisioning path is the real home (one seed per new org DB), with a manual flag/CLI for dev. Decide alongside the provisioning work.

Source: Spectrum seed plan — the seed function is built; wiring was deliberately deferred.

`db::seed::seed_spectrum_cataloguing` exists and is idempotent, but nothing invokes it yet. Decide how/when an org's baseline field set gets seeded: - a `server --seed` / config flag that runs it on startup, and/or - a small CLI subcommand, and/or - part of per-org provisioning (the control plane), so a freshly-provisioned org gets the baseline Spectrum fields automatically. Likely the provisioning path is the real home (one seed per new org DB), with a manual flag/CLI for dev. Decide alongside the provisioning work. _Source: Spectrum seed plan — the seed function is built; wiring was deliberately deferred._
logaritmisk commented 2026-06-06 05:18:49 +00:00
Author
Owner
Copy Link
Copy Source

Done in 8ed747c (merged to main). Wired via a server seed CLI subcommand mirroring create-user: it connects, applies migrations (idempotent — so it works on a fresh DB), then runs db::seed::seed_spectrum_cataloguing in a transaction and commits. Safe to re-run. Added a just seed recipe and a README "Running locally" step. The per-org provisioning path is deferred until a control plane exists (none yet — single-tenant).

Done in `8ed747c` (merged to `main`). Wired via a **`server seed`** CLI subcommand mirroring `create-user`: it connects, applies migrations (idempotent — so it works on a fresh DB), then runs `db::seed::seed_spectrum_cataloguing` in a transaction and commits. Safe to re-run. Added a `just seed` recipe and a README "Running locally" step. The per-org provisioning path is deferred until a control plane exists (none yet — single-tenant).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
logaritmisk
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: logaritmisk/biggus-dickus#14
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?