Skip to content

v0.2.0

Choose a tag to compare

View all tags
@StephenODea54 StephenODea54 released this 09 Sep 19:37
· 15 commits to main since this release
v0.2.0
8ffe520

Docket can now run anywhere: as a container, inside AWS Lambda, and against a catalog shared through S3.

What's new

  • Container image — ghcr.io/stephenodea54/docket is built and published on every push to main and on version tags. It bundles the CLI, the web UI, the Steampipe extension, and the lambda extra.
  • docket serve --adapter uvicorn|lambda — serve adapters pick how the web UI is hosted. uvicorn binds a socket as before; lambda wraps the app with Mangum and runs the Lambda Runtime Interface Client, so the image deploys as a Lambda function behind API Gateway, an ALB, or a Function URL with no wrapper. DOCKET_SERVE_ADAPTER sets the default.
  • S3 catalog store — DOCKET_DB_PATH accepts an s3://bucket/key uri as well as a local path. Every command pulls the object to a local cache first (~/.docket/cache/, or /tmp when home is read-only); docket run pushes on success and docket audit pushes after recording new events. Local paths behave exactly as before.
  • Issue and pull request templates, and a README covering installation, configuration, and every CLI command.

Upgrading

No breaking changes. docket serve without --adapter still runs uvicorn, and a plain DOCKET_DB_PATH still opens the file in place. Install the lambda extra (uv sync --extra lambda, Linux only) to use the lambda adapter outside the published image.

Requirements

Python 3.11+, managed with uv.

Assets 2
Loading