One Compose for the whole host surface
Postgres, MinIO, Redis, Qdrant, Ray, Airflow, Grafana, Prometheus, and Streamlit come up together. This is the physical surface on which Framework executes DRTML — not a loose collection of containers.
DrToller.Platform
The deploy stack that hosts a DRTML runtime.
OSS Docker Compose stack and operator CLI forDrToller.Framework. Platform wires Postgres, MinIO, Redis, Qdrant, Ray, Airflow, Grafana, Prometheus, and Streamlit. Step packs are not bundled — mount Edge and/or Ops. The runtime stays in Framework.
Operator contract, not a pile of scripts
drtoller up, down, verify, update, and env cover bring-up, Postgres migrate, Grafana sync, and health. Partial start/stop exists; the default path is one command.
Deploy layer, not the runtime
Platform owns compose, env, bootstrap, and host wiring. Framework owns DRTML compile, storage, processing, and metrics emit. Edge and Ops own step domain logic and are mounted in — not shipped inside the stack.
Airflow and Streamlit host the contract
Thin DAG wrappers and the step launcher UI call Framework. Steps do not know about DAGs or widgets. Airflow answers when to run; DRTML answers what the workload is.
Dashboards provisioned with the stack
Prometheus and Grafana start with the compose project. Pipeline dashboards and Postgres DDL are generated from DRTML at up/update — not hand-maintained JSON in git.
Local Ray, then KubeRay attach
Compose runs a Ray head for single-host work. Multi-host is drtoller cloud bootstrap onto an existing DOKS cluster (KubeRay). AWS and GCP installers are backlog — not promised here.