Files

T

woggioni 25af0bf3fe Document every API response body in the OpenAPI spec

kaya-openapi 0.0.8 supports named component schemas, so the routes'
description-only responses become $refs: schemas for the core payloads
(auth providers, lobby, game view, ongoing games, match history,
leaderboard, ratings) live in tavolo.platform.openapi and are registered
through the mixin's components. Engine-defined parts (options echo, game
views, match results) stay open objects on purpose. Error responses now
carry the error envelope schema, and a new suite sweeps the document to
keep every /api response typed.

2026-10-14 14:05:11 +00:00

src/tavolo

Document every API response body in the OpenAPI spec

2026-10-14 14:05:11 +00:00

pyproject.toml

Add scopa: classic two-player and scopa a quattro

2026-10-09 05:39:00 +00:00

README.md

Add scopa: classic two-player and scopa a quattro

2026-10-09 05:39:00 +00:00

README.md

tavolo-app

The deployable tavolo application: the composition root wiring tavolo-platform to the tavolo-scopone, tavolo-scopa and tavolo-briscola games.

app.py — assembles the KayaApp (session/OIDC/Tortoise/OpenAPI mixins plus PlatformMixin and the deadline scheduler), registers the ScoponeEngine, ScopaEngine, ScopaQuattroEngine, BriscolaEngine, BriscolaQuattroEngine and BriscolaChiamataEngine with their configured timeouts, and exposes tavolo.app:app for granian.
config.py — environment-driven frozen Settings.
telemetry.py — the optional OpenTelemetry wiring beyond kaya-otel: meter/tracer/logger providers, the tavolo.active_users/tavolo.ongoing_games gauges (polled from the stores), process/CPython metrics via opentelemetry-instrumentation-system-metrics, Postgres/Redis query spans via the asyncpg/redis instrumentations, and OTLP log export.
aerich_config.py — Tortoise ORM configuration consumed by the aerich CLI (migrations live in server/migrations/; aerich itself is configured via the [tool.aerich] section of server/pyproject.toml).
logging_config.py — logging setup.
static.py — SPA shell hosting for the compiled frontend.

Development (from `packages/tavolo-app/`)

.venv/bin/python -m mypy --namespace-packages --explicit-package-bases \
  src/tavolo/app.py \
  src/tavolo/config.py \
  src/tavolo/telemetry.py \
  src/tavolo/static.py \
  src/tavolo/aerich_config.py \
  src/tavolo/logging_config.py

End-to-end coverage of the wired stack lives in server/tests/.

README.md

tavolo-app

Contents

Development (from packages/tavolo-app/)

Development (from `packages/tavolo-app/`)