Documentation
¶
Overview ¶
Command lcatd-lambda serves the libcat dynamic backend under AWS Lambda behind a Function URL (or API Gateway v2 HTTP API; both deliver the v2 HTTP payload). provided.al2023, handler "bootstrap". It builds the same handler as cmd/lcatd from the same LCATD_* environment, so a read-only demo runs on Lambda with the SPA embedded and no persistent AWS services (in-memory store + a bundled read-only grain dir).
A writable deployment (DynamoDB + S3 via LCATD_DYNAMO_TABLE / LCATD_S3_BUCKET) additionally needs its queued work drained: container tickers freeze between invocations, so the function also accepts the scheduled drain event {"lcatd":"drain"} (an EventBridge rule in the terraform stack) and runs the vocab-download and export-job drains once per firing instead (tasks/099).