tiltlisted

# Tilt Development Environment ## Automatic Reload Behaviors Tilt live-reloads aggressively. **Never suggest restarting `tilt up` or manually refreshing resources**—Tilt handles this automatically in nearly all cases. ### What Reloads Automatically | Change Type | What Happens | Your Action | |------------|--------------|-------------| | **Tiltfile edits** | Tilt re-evaluates the entire Tiltfile on save | Just save the file | | **Source code with `live_update`** | Files sync to container without rebuild | Just save the file | | **Source code without `live_update`** | Full image rebuild triggers automatically | Just save the file | | **Kubernetes manifests** | Resources re-apply automatically | Just save the file | | **Frontend with HMR** | Browser updates via Hot Module Replacement | Just save the file | | **Backend with watch tools** | Process restarts via nodemon/air/watchexec | Just save the file | ### When Restart IS Actually Needed Restarting `tilt up` is required only for: - Tilt version upgrades - Changing Tilt's port or host settings - Recovering from Tilt crashes - Kubernetes context changes (switching clusters) ### Verifying Updates Applied Instead of restarting, verify updates propagated: ```bash # Check resource status after saving tilt get uiresource/<name> -o json | jq '.status.updateStatus' # Watch for update completion tilt wait --for=condition=Ready uiresource/<name> --timeout=60s # Check recent logs for reload confirmation tilt logs <resource> --s