REST API to PostgreSQL Task Board

How it works

This LoT Notebook turns a task tracker into a broker-first flow on Coreflux LoT. A REST_API route accepts create, complete, remove, and refresh requests, while a POSTGRESQL route writes and reads task data and publishes results to MQTT topics.

Key features

• HTTP ingress: /tasks and mutation endpoints accept REST requests in server mode.
• PostgreSQL persistence: inserts, updates, deletes, and SELECT views run through a database route.
• MQTT egress: task lists, due-today views, KPIs, and domain events land on demo/tasks/# topics.
• Daily reporting: weekday triggers compose into a midnight report on demo/tasks/reports/daily.
• Topic-backed metrics: created, completed, removed, and error counters are kept on domain topics.

Prerequisites

• PostgreSQL reachable from the broker
• TASKS_DB_HOST, TASKS_DB_NAME, TASKS_DB_USER
• TASKS_DB_PASSWORD stored as a secret
• A free server port for the REST_API route