Serve SQLite Database

How it fits

Typical backends

Caveats

• I/O contractThis component has no pipeline inputs or outputs; it serves an HTTP endpoint over a SQLite file that some other process populates, returning all columns of each row ordered newest-first with no projection.
• Hard constraintThe database is opened read-only, so the file must already exist and be populated out-of-band; the endpoint never writes, creates or migrates the table.
• Parameter interactionA request limit above max_limit is silently clamped, and a request with no limit uses default_limit; the time-window parameters filter on a received-timestamp column when present.
• State lifetimedb_path, table and the bearer token are fixed at deploy time and require a redeploy to change, while the limits and busy timeout can be adjusted at runtime.
• CompatibilityResponses set permissive cross-origin headers and the health check is unauthenticated even when a bearer token is set, so place sensitive deployments behind an additional access gate.
• Hard constraintThe table name must be a plain alphanumeric identifier; an unusual name fails validation at startup.