Petrolyst server infrastructure: Traefik, Trino and Superset

Traefik as the server-wide edge (TLS via Let's Encrypt, dashboard on
traefik.petrolyst.com behind oauth2-proxy and Keycloak). The
fuel-monitoring stack: Superset on atoma.petrolyst.com with Keycloak login
and Petrolyst branding, Trino reading the TimescaleDB fuel-db as catalog
"fuel". Customization lives in petrolyst-insights/, deployment in the other
folders.

Deploys run server-side (deploy/deploy.sh) from a Gitea workflow or
manually; releases are immutable, Superset metadata is backed up before
migrations, and deploy/rollback.sh restores it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

stacks/fuel-monitoring/trino/etc/config.properties

@@ -0,0 +1,14 @@
+# Single node: coordinator and worker in one process. Reachable only on the
+# backend network (Superset); no port is published and Traefik has no route.
+coordinator=true
+node-scheduler.include-coordinator=true
+http-server.http.port=8080
+discovery.uri=http://localhost:8080
+catalog.management=static
+
+# Memory bounds. The container is capped at 3g (compose.yaml) and jvm.config
+# gives the heap 75 % of it (~2.25 GB); 1 GB for queries plus 512 MB headroom
+# leaves room for the rest of the heap.
+query.max-memory=1GB
+query.max-memory-per-node=1GB
+memory.heap-headroom-per-node=512MB