Users & admins

There is no sign-up page

Playdex is built for small, invite-only instances. Users can’t register themselves. You create every account in the database.

Create a user

Passwords are stored as bcrypt hashes. Generate one, then insert the row:

Python

python3 -c "import bcrypt,getpass;print(bcrypt.hashpw(getpass.getpass().encode(),bcrypt.gensalt()).decode())"

(pip install bcrypt first if needed.)

Docker (no installs)

docker run --rm httpd:2.4-alpine htpasswd -nbBC 11 "" 'their-password' | cut -d: -f2

In the browser

The config builder hashes a password locally. Fill in First administrator and copy the hash out of create-admin.sql.

docker compose -f docker-compose.prod.yml exec db psql -U playdex -d playdex

insert into users (email, password) values ('friend@example.com', '$2b$11$…');

Send them the Web URL and their password. They can connect gaming accounts and set up notifications themselves under Settings.

Tip

Emails are compared exactly at login (only surrounding spaces are trimmed). Friend@Example.com and friend@example.com are different accounts, so store emails lowercase.

Make someone an admin

update users set is_admin = true  where email = 'friend@example.com';   -- promote
update users set is_admin = false where email = 'friend@example.com';   -- revoke

Admin checks is_admin against the database on every action, so a revoke takes effect immediately, even for an open session.

Reset a password

update users set password = '$2b$11$…new hash…', updated_at = now() where email = 'friend@example.com';

Existing Web sessions stay valid until their tokens expire: 15 minutes for the access token, 30 days for the refresh token. To sign everyone out at once, change Auth__JwtSecret and restart the API.

Delete a user

delete from users where email = 'friend@example.com';

This cascades to their sessions, integrations, notification channels and AI history.