Server deployment: Docker, Compose and Helm

Server deployment: Docker, Compose and HelmThe container image, the rules every server deployment must satisfy, the Compose stack, the Helm chart and the vault key. The server edition is the backend (API and web client) in one container image. The rules below are enforced by the server itself, not by the deployment files, so they apply however you run it. Per-user roles come from Entra ID sign-in on top of the token. See Sign-in and roles.

What this page covers

The rules every deployment must satisfy
The image
Docker Compose (deploy/compose)
Helm (deploy/helm/analytics-table)
The vault key in a container
Resource limits and health

Settings and controls documented

X.Y.Z, X.Y
latest
main, sha-<short>
existingSecret
ingress
config.webOrigin
config.allowedOrigins
resources
spill.sizeLimit
persistence.size / accessMode
networkPolicy.enabled
podDisruptionBudget.enabled
shutdownGraceSeconds
autoscaling
Mounted key file (recommended)
External vault
Accept the risk
ANALYTICS_QUERY_TIMEOUT_S
ANALYTICS_BACKGROUND_TIMEOUT_S
ANALYTICS_MAX_RESULT_MB
ANALYTICS_MAX_INTERACTIVE_QUERIES
ANALYTICS_MAX_BACKGROUND_QUERIES
ANALYTICS_QUEUE_WAIT_S
ANALYTICS_IDLE_SHUTDOWN_H
ANALYTICS_DUCKDB_TEMP_DIR / ANALYTICS_DUCKDB_MAX_TEMP_MB

Full page

The full page — procedures and the explanation of every setting — is available to signed-in users.

ATX Institute — home

Products

Company

Resources

Guides

ATX Institute on LinkedIn

This site needs JavaScript for the full experience. Every page above is reachable without it.