aiolabs/nsecbunkerd
8
0
Fork 0
Code Issues 12 Pull requests Projects Releases Packages Wiki Activity Actions

docs: correct prisma-engines + migrate-on-boot accuracy in runbook
Some checks failed
Docker image / build-and-push-image (push) Has been cancelled
Details

Browse source 
- nix devShell uses nixos-25.05's prisma-engines 6.7.0 (has
  libquery_engine.node) — the 7.x problem is the system/unstable channel
  only, not the flake's devShell (corrects an earlier overstatement; #30
  closed as invalid).
- start.js migrate-on-boot is a no-op on nix but IS the migration path on
  docker (image ENTRYPOINT) — don't assume it's dead everywhere (#31).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Padreug 2026-06-20 20:50:21 +02:00
commit 87e99e487e
1 changed files with 13 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

18
docs/runbook-migrations.md
View file

@ -56,10 +56,16 @@ wipe loses ACL/pairing state, never keys. LNbits holds the bunker **admin nsec**
## Schema migrations ## Schema migrations
Migrations are applied by the deploy's `prisma migrate deploy`, **not** by the On the **nix deploy**, migrations are applied by the deploy's `prisma migrate
daemon on boot — the in-`start.js` `npm run prisma:migrate` step is a no-op deploy`, not by the daemon — `start.js`'s `npm run prisma:migrate` step fails in
(tracked in #31). After adding a migration, make sure the deploy applies it. the read-only nix store (no `npm` on PATH) and is a redundant no-op there (#31).
On **docker**, by contrast, `start.js` IS the migration path (it's the image
`ENTRYPOINT`), so the step is not dead everywhere. After adding a migration, make
sure the path that applies for your target actually runs it.
Prisma on NixOS needs the engine env pinned to `prisma-engines_6` (the bare Prisma on NixOS: the flake pins **nixos-25.05**, whose `prisma-engines` is
`prisma-engines` attr is now 7.x with no `libquery_engine.node`; devShell fix **6.7.0** (ships `libquery_engine.node`) — both the devShell and the deploy's
tracked in #30). The deploy's `package.nix` already pins `_6`. `package.nix` use it, so `prisma` (and the `npm run test:integration` suite) work
in `nix develop` out of the box. Heads-up: on **nixos-unstable / a system
`<nixpkgs>` channel**, the bare `prisma-engines` attr is 7.x with no
`libquery_engine.node`; don't run the repo's prisma against an unstable channel.