Where Is the Tiltfile?
Tilt reads Tiltfile at the project root for builds, deploys, and live update rules per service.
Last updated
Tilt configures from a Starlark file at the project root. The Tiltfile names Docker builds, Kubernetes applies, and live update steps per service. Extensions load from the same folder or a shared path.
No global config matters for daily work. Per project files keep environments reproducible across machines. Version drift shows as deprecated function warnings, so match guides to the installed release.
Where Tilt stores this, by platform
[ProjectDir]/Tiltfile
Builds, deploys, and update rules in Starlark live here. Extensions resolve beside it. Keep the file with manifests it drives.
[ProjectDir]/Tiltfile
Same root file on Mac. Live update syncs sources into running containers. Profiles per cluster go in the same file.
[ProjectDir]\Tiltfile
Same file on Windows. Path handling inside follows the project root. Exact function names vary by Tilt release.
Frequently asked questions
How do I run only one service?
Label services in the Tiltfile and select with the run flags. Labels group related workloads. The file stays the single source for all sets.
Why does Tilt ignore my Dockerfile change?
Live update rules sync sources without rebuilding, so image changes need a full build trigger. Check the update mode per resource. The Tiltfile decides which path applies.
Notice an outdated path? Let us know.