vaultwarden: compose header matches invite-first; live proof lines (R-512/R-514)
gates / gates (push) Successful in 1s
gates / gates (push) Successful in 1s
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
This commit is contained in:
@@ -19,6 +19,12 @@ templates changed.
|
||||
Now 1 × 1 and `memory: 1280M` (peak × 1.5, rounded up to 256M); `mem_limit` hint 1664M. Caveat
|
||||
recorded: the test PDFs carried text, so OCR on scanned images may need more — the controller's new
|
||||
OOM line (controller v0.243.0) makes that visible if it happens.
|
||||
- **Vaultwarden compose header** no longer tells the reader to "Set SIGNUPS_ALLOWED=false via the
|
||||
controller" (settings are read-only after install); it describes the invite-first steps. **Proven
|
||||
live 2026-09-15 on scratch 9202:** deployed from the catalog through the controller API, container
|
||||
`SIGNUPS_ALLOWED=false`, a stranger's `send-verification-email` through traefik → **400 „Registration
|
||||
not allowed"**; Paperless deployed the same way: 20 PDFs at once → **20/20 SUCCESS**, `memory.peak`
|
||||
772 370 432 B under the 1280M cap, no OOM.
|
||||
- **R-515 — the Paperless card no longer says `admin / admin`.** That login never existed (the
|
||||
password is generated). `default_creds` removed; first steps point at „Automatikusan generált
|
||||
értékek", the gokapi wording.
|
||||
|
||||
Reference in New Issue
Block a user