Zero-config first run (https://github.com/libredb/libredb-studio/releases/tag/0.9.41)

LibreDB Studio now starts with no configuration at all. When JWT_SECRET and/or ADMIN_PASSWORD are not set, the server generates the missing values on first start, stores them in /auth-bootstrap.json (file mode 0600, atomic write), and prints the admin password once to the server log. Explicitly set environment variables always take precedence, and restarts reuse the persisted credentials.

docker run -p 3000:3000 ghcr.io/libredb/libredb-studio:latest now works with zero environment variables.

AUTH_BOOTSTRAP=off (also false/0, case-insensitive) restores the strict behavior: missing variables surface as a clear login error instead of generated credentials. Recommended for production deployments with central log collection.

OIDC mode (NEXT_PUBLIC_AUTH_PROVIDER=oidc) generates only the JWT secret; a password is never generated.

Every bootstrap error fails open to the previous strict behavior; corrupt or wrong-shape credential files are moved to .bak and regenerated. The JWT secret is never logged.

Helm and existing Docker deployments that set env vars are unaffected: bootstrap is a no-op that performs no filesystem access when credentials are provided.