Skip to content

What it is

kbve.com’s /@{user} pages and the account API beside them: /api/v1/profile/{user}, /api/v1/profile/me, POST /api/v1/profile/username, /api/v1/me and /api/v1/me/staff. A profile is read from Supabase and enriched from Discord, Twitch and RentEarth, cached in memory for five minutes. Signed-in routes verify the session against Supabase Auth through jedi::jwt_cache, so a revoked session stops working before its token expires.

The page’s markup

The site owns it. kbve-web’s build renders docs/askama/profile.mdx into an askama template styled with the site’s bundles, and this image compiles that template in, copied from the kbve-web image the Dockerfile’s KBVE_WEB pins. The committed templates are stubs for local builds. A site release that changes the profile page reaches it when that pin moves and this service releases.

Where it came from

Moved out of axum-kbve with the same paths, status codes and JSON. /@{user}/ now redirects to /@{user} instead of 404ing. /api/v1/auth/game-token stayed behind with the game server it belongs to.

Releasing

Bump version: above. The kbve-profile job publishes the image and kbve-profile-deploy opens the merge request that repoints kbve-profile-deployment.yaml.

Discuss on the forum

Questions, fixes and notes on this page live in the KBVE forum.