How tilt-dev/tilt works
Tilt is a local development orchestrator for multi-service applications. A user starts it with tilt up; Tiltfile configuration describes resources, and Tilt watches files, builds images or commands, and updates Kubernetes or Docker Compose environments. Controllers and shared engine state coordinate that work, while the local HUD and web client expose status and logs. The README documents the end-to-end development loop; sampled excerpts show selected controller, state, and server behavior, but not all subsystem wiring.
Main entry points: up.go Tilt CLI · build_and_deployer.go Build and deploy · engine_state.go Engine state · server.go HUD server
Components 19
User entry
- Tilt CLI
internal/cli/up.go
Configuration and state
- Tiltfile evaluation
internal/tiltfile/tiltfile.go - Engine state
internal/store/engine_state.go
Build and runtime
- File watching
internal/controllers/core/filewatch/controller.go - Build controller
internal/engine/buildcontroller.go - Build and deploy
internal/engine/buildcontrol/build_and_deployer.go - Docker client
internal/docker/client.go - Compose client
internal/dockercompose/client.go - Kubernetes client
internal/k8s/client.go - Command controller
internal/controllers/core/cmd/controller.go - Local process manager
internal/engine/local/servercontroller.go - Pod log streams
internal/controllers/core/podlogstream/podlogstreamcontroller.go
Status and interface
- HUD server
internal/hud/server/server.go - Web client state
web/src/HudState.tsx - Web log store
web/src/LogStore.ts
Other components
- Developer
- Browser user
- Kubernetes cluster
- Compose environment
Connections 19
- Developer → Tilt CLI: runs tilt up
README.md - Tilt CLI → Tiltfile evaluation: starts configuration
- Tilt CLI → Engine state: dispatches actions
- Tilt CLI → Tiltfile evaluation: invokes CLI
- File watching → Engine state: dispatches updates
internal/controllers/core/filewatch/controller.go - Build controller → Engine state: reads build state
internal/engine/buildcontroller.go - Build controller → Build and deploy: runs builds
internal/engine/buildcontroller.go - Build and deploy → Docker client: builds images
- Build and deploy → Compose client: deploys services
- Build and deploy → Kubernetes client: applies workloads
- Docker client → Kubernetes cluster: provides images
- Compose client → Compose environment: updates services
- Kubernetes client → Kubernetes cluster: manages resources
- Command controller → Local process manager: starts commands
internal/controllers/core/cmd/controller.go - Pod log streams → Kubernetes client: reads pod logs
internal/controllers/core/podlogstream/podlogstreamcontroller.go - HUD server → Engine state: reads and dispatches
internal/hud/server/server.go - Browser user → HUD server: requests HUD
- Web client state → Web log store: uses log state
web/src/HudState.tsx - HUD server → Web client state: serves interface