Niklas Ye
536dbcaebe
Users now have an avatar. The account page takes an image, lets the user
drag and zoom it under a circular mask, and uploads exactly what the circle
shows as a 256x256 PNG. The picture replaces the initial-letter circle in
the sidebar, on the account page, on the on-call hero and week strip, on
the schedule's day chips and in the incident assign menu; someone without
one keeps the initial.
The picture lives in Postgres (user_avatars, bytea) rather than on a
volume: the chart runs two replicas on a read-only root filesystem, and
the k8up pg_dump backup then covers it without any chart or operator
change. The server does not trust the client's crop. It decodes the PNG or
JPEG, checks the declared size before decoding, centre-crops to a square,
scales to 256 and re-encodes, which drops EXIF and anything that is not
pixels. Standard library only; WebP is cropped by the browser and arrives
as PNG, a raw WebP sent to the API is refused.
GET/PUT/DELETE /api/users/{id}/avatar: anyone signed in may read, only the
owner or an administrator may change. /api/me and /api/users gain
avatar_version, absent when there is no picture, which is also the ?v= that
busts the cache after a change. Incident timeline entries and the queue are
text-only and are unchanged.
Claude-Session: https://claude.ai/code/session_016mBLURvJoMuUEr9cB2RpUN
12 lines
546 B
SQL
12 lines
546 B
SQL
-- A user's profile picture: one already-cropped, re-encoded 256x256 PNG per
|
|
-- user. Kept in Postgres rather than on a volume so every replica serves it and
|
|
-- the pg_dump backup covers it. updated_at is in milliseconds, not seconds like
|
|
-- the other timestamps, because it doubles as the cache-busting version of the
|
|
-- image URL and a re-upload within the same second must change it.
|
|
|
|
CREATE TABLE user_avatars (
|
|
user_id bigint PRIMARY KEY REFERENCES users(id) ON DELETE CASCADE,
|
|
data bytea NOT NULL,
|
|
updated_at bigint NOT NULL
|
|
);
|