Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/developers/architecture.md
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,7 @@ A running RomM container hosts several cooperating processes:

## Request lifecycle

Every request runs the middleware stack in order, CORS → CSRF → authentication → Valkey-backed session → context vars (aiohttp + httpx clients), before FastAPI dispatches to the endpoint. Handlers do the actual work and Pydantic schemas serialise the response.
Every request runs the middleware stack in order, CORS → CSRF → authentication → Valkey-backed session → context vars (aiohttp + httpx2 clients), before FastAPI dispatches to the endpoint. Handlers do the actual work and Pydantic schemas serialise the response.

## Backend

Expand Down
2 changes: 1 addition & 1 deletion scripts/gen_platforms.py
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@

Strategy: shell out to the upstream generator at
`backend/utils/generate_supported_platforms.py`. That module imports the
full romm handler stack (redis, db, httpx), so it has to run inside
full romm handler stack (redis, db, httpx2), so it has to run inside
romm's own uv environment, not this one.

Set `ROMM_SRC` to the romm checkout root (read from .env at the repo root
Expand Down
Loading