.env.example
Set these on your host before deploying. Each platform has an “Environment Variables” section in the deploy flow.
PG_USER
Postgres metastore (the docker-compose Postgres service) PG_DBNAME is the CONTROL-PLANE database. Liquibase creates the `qodstate_*` tables…
PG_PASSWORD
secret
PG_DBNAME
PG_SCHEMA
PG_PORT
Host-exposed port for the in-compose Postgres. Bump if the host already runs Postgres on 5432 the internal container port stays 5432, the…
AUTH
Quack-on-demand auth + TLS AUTH gates BOTH the FlightSQL edge AND the admin UI / REST API: true → DB-backed auth, admin user seeded from…
ADMIN_USERNAME
Seeded into qodstate_user (as a superuser: tenant IS NULL) when AUTH=true. ROTATE the password before exposing the edge beyond localhost.
ADMIN_PASSWORD
secret
API_KEY
secret
Optional static REST key. Blank = no static key; clients authenticate via the UI login flow and a session token. Set to bypass login with…
TLS
`true` enables FlightSQL edge TLS (cert auto-generated under ./certs). When `true`, the tpch-load-test's --url must be grpc+tls://… ; when…
MANAGER_PORT
Host ports Only two ports are part of the public contract and need to be reachable by users / BI tools: MANAGER_PORT (20900) Manager REST…
EDGE_PORT
QUACK_MIN_PORT
QUACK_MAX_PORT
TPCH_SF
Optional one-shot TPCH loader Generates TPCH data into the bootstrap tenant-db (`tpch_tpch1` by default) via DuckDB's dbgen() table…
TPCH_SCHEMA
brew install flyctl && fly launch --from https://github.com/starlake-ai/quack-on-demand
curl -L https://fly.io/install.sh | sh && fly launch --from https://github.com/starlake-ai/quack-on-demand
iwr https://fly.io/install.ps1 -useb | iex; fly launch --from https://github.com/starlake-ai/quack-on-demand