Operating it
Dashboard login
Way back in when you lose the admin login.
Passwords
- bcrypt, configured through Better Auth's hasher hooks. That is what lets the hub sync the admin account without importing Better Auth into the database package.
- Changing someone's password deletes their sessions, signing them out everywhere.
ADMIN_EMAILmust be a well-formed address.admin@localhostis rejected.- There is one account and no sign-up, so changing
ADMIN_EMAILrenames it on the next boot instead of adding a second admin. Sessions survive the rename; the old address does not.
Locked out?
The hub syncs the admin account to ADMIN_EMAIL/ADMIN_PASSWORD on every
boot. Change ADMIN_PASSWORD and bring the hub up again — that is the
way back in, and it is why both live on the hub service's environment
rather than in a file inside the container.
docker compose --env-file .env -f deploy/docker-compose.yml up -d hubrestart is not enough: it starts the same container again, with the
environment it was created with. up -d sees the changed value and
replaces the container.