Installer + backend: seed the bootstrap admin password
The installer now asks during the wizard whether to auto-generate or type a password for the BOOTSTRAP_ADMIN_EMAIL account. The value is written to .env.compose as BOOTSTRAP_ADMIN_PASSWORD (and into the secrets-backup file), and surfaced in the post-install final report so the operator can sign in immediately at /login without going through the signup form first. Backend ensureBootstrapAdmin() now creates the user with the supplied password (hashed via bcrypt, cost 12) if the email doesn't yet exist. Password must be >= 12 chars or the seeding step is skipped. onboarded_at is left null so the first sign-in still goes through the onboarding wizard. The legacy "sign up via the form, get auto-promoted to admin" behaviour remains intact when BOOTSTRAP_ADMIN_PASSWORD is empty.
| Repository | cpatpa/PIP |
|---|---|
| Author | Claude <noreply@anthropic.com> |
| Authored | |
| Parents | 56e15d04 |
| Stats | 4 files changed , +121 , -4 |
| Part of | Bootstrap admin password seeding (installer + backend) |
Capture this commit into my fork
Download a Markdown prompt that tells Claude how to port this
exact commit into your working tree. Run it via
claude -p < capture-commit-fcc68098.md
from inside the repo you want the change in.