6fd2d7c981
Run Thermograph as a docker-compose stack (app + Postgres 18) and standardize the
data layer on Postgres, while keeping the test suite on SQLite.
- accounts/db.py: DSN-driven engines. On Postgres, a per-worker read-write +
read-only asyncpg pair (the RO engine pins read-only transactions, used by the
pure-GET endpoints) plus a sync psycopg engine for the notifier thread; the
SQLite path is preserved for tests/local (selected when THERMOGRAPH_DATABASE_URL
is unset). models.py: boolean server_default -> sa.false().
- store.py / metrics.py: dialect-flexible — Postgres UNLOGGED tables via psycopg
when configured, else the existing raw-sqlite3 paths byte-for-byte; sync
interfaces and every fail-soft contract preserved.
- Alembic (backend/alembic/) manages the accounts schema; the container entrypoint
runs `alembic upgrade head` before uvicorn (4 workers). migrate_accounts_to_pg.py
copies the accounts data SQLite->PG through the ORM (UUID/bool/JSON coerced),
skips access_token, and resets identity sequences.
- Dockerfile + docker-compose.yml: app image (uvicorn, 4 workers, loopback 8137)
and a Postgres 18 db (2 CPUs) running pg_duckdb (deploy/db/) so the parquet
climate cache is queryable in-DB via read_parquet('/parquet/cache/*.parquet').
- deploy.sh/thermograph.service rewired to manage the compose stack; env example,
Makefile targets (up/down/db-up), and deploy/POSTGRES-MIGRATION.md cutover runbook.
Tests stay on SQLite (dialect fallback) — 323 pass. The full Postgres stack was
verified via docker compose: alembic migrations, register/login, the RO endpoint,
store/metrics round-trips, and the accounts data migration.
15 lines
795 B
SQL
15 lines
795 B
SQL
-- Enable pg_duckdb so the database can read the app's Parquet climate cache
|
|
-- directly (ad-hoc analytics via DuckDB's read_parquet / read_csv / etc.).
|
|
--
|
|
-- This runs once, on first cluster init (empty PGDATA), from
|
|
-- /docker-entrypoint-initdb.d. Because the compose `db` service keeps its data
|
|
-- on a persistent named volume, init scripts do NOT re-run on an existing
|
|
-- database -- to enable pg_duckdb on a DB that was created before this image,
|
|
-- run it by hand:
|
|
--
|
|
-- docker compose exec db psql -U thermograph -d thermograph \
|
|
-- -c 'CREATE EXTENSION IF NOT EXISTS pg_duckdb;'
|
|
--
|
|
-- pg_duckdb requires shared_preload_libraries='pg_duckdb'; the base image's
|
|
-- postgresql.conf.sample already sets it, so it is active on fresh init.
|
|
CREATE EXTENSION IF NOT EXISTS pg_duckdb;
|