meadows-web

MEADOWS web host: a dumb HTTP host that serves index.html and static assets. No Socket.IO, no auth, no domain logic. The browser is the client; the Socket.IO connection runs browser→meadows-server, NOT via this Python webserver. See MEADOWS-migration-intent.md section 2 line 40 and section 4 line 115.

Architecture

graph LR
    B[Browser<br>JS] -->|Socket.IO| S[meadows-server<br>:8080]
    B -->|HTTP| W[meadows-web<br>:8081]
    W -.->|static files only| B

The browser connects directly to meadows-server via Socket.IO. This Python server is just a file host.

What this package contains

• app.py — the Starlette ASGI app. Serves / → dist/index.html and /static/* → assets. Nothing else.
• build.py — template injection: reads templates/index.html, injects protocol constants + env config, writes dist/index.html.
• templates/index.html — minimal webchat page (Socket.IO client in the browser).
• __main__.py — python -m meadows.web entrypoint (uvicorn).

Install

uv pip install -e ".[dev]"

This pulls in meadows-protocol (editable, via the sibling path) — the only MEADOWS dependency. The web host touches meadows.protocol solely to inject EventName constants into the template. It does not import Message, JWTClaims, or any domain model.

Build the template

uv run python -m meadows.web.build

Run

uv run python -m meadows.web
# or
uv run uvicorn meadows.web.app:app --host 0.0.0.0 --port 8081

Test

uv run pytest -q

Architecture invariants

1. Dumb host. No Socket.IO, no auth, no JWT, no message parsing. It serves files. Period.
2. TLS is not a concern. Traefik terminates TLS (section 4 line 115). No cert logic here.
3. Protocol constants only. The only import from meadows.protocol is EventName (for template injection).
4. PEP 420 namespace. src/meadows/web/__init__.py exists; there is NO src/meadows/__init__.py.

Configuration (env vars, managed via check_env in tasks.py:setup)