Crasho
26270e9c25
* rrs stuff * studio service yay * rrs whitelist * moree studiooooooo fellowwww * rec room studio room loading yay * fixes yay * fix 2 because idk yayuh * Update cdn.app.ts * ccontent length fix? * Preserve content-length and upgrade metadata Return a real zero-filled byte array for CDN HEAD responses so the runtime preserves Content-Length while still sending no payload. In notify, re-create the Request with its original headers, set OWNER_HEADER from the validated token, and forward that Request to hub.fetch to avoid losing WebSocket upgrade metadata (which could trigger 500s in Durable Objects). These changes ensure the editor's size checks and WebSocket upgrades remain reliable. * fix x524234 * shirt thing? * [auth] remove grant table as we already have audit_log for now * rename table to generic device_grant * cleanup/lint --------- Co-authored-by: Devin Zuczek <devin.zuczek@gmail.com>
rooms
Room Worker served on the rooms subdomain (rooms.recflare.net) — a Hono app owning
room storage, the browse/search feeds, per-player cheers and favorites, the owner's room
settings, and subrooms.
Rooms live in the shared recflare D1 as one JSON blob per room (queryable fields are
SQLite generated columns); reads serve that blob verbatim, which is why every shape is
the client's PascalCase one. Subrooms are their own table — their ids come from a single
global sequence, not per room — and are re-attached to each room on read. The seed rooms,
including the dorm, come from static/ImportRooms.json.
API documentation
GET /openapi.json serves a spec generated from describeRoute blocks that sit
alongside each handler, with the schemas in src/openapi.ts. It's also aggregated into
the docs page www serves at /docs.
The spec is descriptive, not enforced — same rationale as the auth/match/clubs
workers: a reverse-engineered protocol, lenient handlers, no runtime validation. A test
asserts every route appears in the spec, so adding one without documenting it fails.
Response envelopes
Two envelopes appear side by side, and which one a route uses is dictated by the client's deserializer for that call — not a choice, and not something to unify:
{ Success, Value, ErrorId, Error }(PascalCase) — a bare result with a message.{ success, error, value }(lowercase) — carries the updated room, which the client re-renders from.
Both answer HTTP 200 even for a rejection: the client reads the flag, not the status. Only a missing or invalid token is a real 401, and only the owner/co-owner gate is a 403.
Reads are the exception: they carry no envelope at all. A paged read (the save history at
…/subrooms/{subRoomId}/saves and its lighter …/saves/no_unity_assets twin) is a bare
{ Results, TotalResults, TotalCount } wrapper — TotalResults and TotalCount are the
same number, because the client's paged DTO and the reference disagree on the name.
GET /rooms/{roomId} puts a Studio build's main bundles on CurrentSave.UnitySubAssets
(target 0 Windows, 2 Android/Quest). unityAssetTarget keeps only that target. Maker-pen
saves keep the arrays empty. GET …/unityasset?unityAssetId= is the bare metadata for
those files; the bytes are on the CDN.
Cron
A */5 * * * * cron (scheduled) sweeps two short-lived tables on the shared database,
neither of them this worker's own:
room_vote(theapiworker's) — vote-to-kick ballots older than 5 minutes. The table is append-only; a vote stays open for 60 seconds and the caller cooldown looks back 5 minutes, so nothing reads an older ballot.room_invite(thematchworker's) — game invites older than 5 minutes (ROOM_INVITE_TTL_SECONDS). Expiry IS the deletion: a redeem that misses the row answersRoomInviteExpired, so the invite prompt goes stale rather than becoming a permanent key into wherever the inviter is later.
The mono facade fires this sweep from its own trigger alongside match's presence sweep.
Development
Run in dev mode
pnpm dev
Run tests
pnpm test
Deploy
pnpm turbo deploy