Skip to content

Deployment ​

Each service ships a multi stage Dockerfile and the same images run everywhere:

TargetWiringGuide
LaptopDocker ComposeRunning and testing
Kubernetes, local or productionKustomize overlays in deploy/k8s/Kubernetes
Any VM over SSH, behind TraefikCompose override in deploy/vm/, make vm-deployAny VM with Traefik
A managed container platformThe platform's own service definitionsREADME

Scaling rules ​

ServiceReplicasWhy
ingestion-serviceAny numberStateless; each connection is independent
fleet-dashboardAny numberStatic and client rendered pages
orchestration-apiExactly oneEvery replica subscribes to the channel, so each would write the same samples to MongoDB. Split persistence into a single worker before scaling out

Documentation site ​

This site is built with VitePress from docs/ and published to GitHub Pages by .github/workflows/pages.yml on every push to main that touches docs/.