docs(wiki): seed-admin on a booth — container-name pattern, prompting form, idempotence, re-seed after a reset
Claude-Session: https://claude.ai/code/session_01FWncR69HgGPuei1dLrW3cU
This commit is contained in:
@@ -350,6 +350,12 @@ docker exec -it -e ADMIN_USER=admin -e ADMIN_PASS='<strong-pw>' \
|
||||
park-buzi-server-1 node scripts/seed-admin.mjs
|
||||
```
|
||||
|
||||
The container is named `<stack>-server-1` (compose project = the Komodo stack name: `park-2-server-1`
|
||||
on park-2; `docker ps` confirms). Leave `ADMIN_USER`/`ADMIN_PASS` off and the script prompts
|
||||
(Enter = `admin`) — preferred on a shared shell, the password never enters history. Idempotent: an
|
||||
existing username is left alone unless `FORCE=1` (§7e). After a `--users`/`--all` reset (§7d) run it
|
||||
again — it recreates the built-in `admin` role row the reset removes.
|
||||
|
||||
> **Secrets-on-disk note.** The generated `.env` lands on the booth with **cleartext** secrets
|
||||
> (compose needs real values). That's why the disk is LUKS-encrypted (§3–4) and keys are per-booth
|
||||
> — the encryption is the control, and a single-booth compromise leaks only that booth's key. See
|
||||
|
||||
Reference in New Issue
Block a user