Tiltfile Study Portal

Quick recall Q&A

1. What problem does Tilt solve?

Tilt eliminates the slow inner development loop of:

1. Make code change
2. Build Docker image
3. Push to registry
4. Update Kubernetes deployment
5. Wait for pod rollout
6. Test change

With Tilt's live update, changes sync in seconds.

2. Explain Live Update vs Full Rebuild

Live Update:

• Syncs changed files directly to running container
• No image rebuild needed
• Sub-second updates
• Best for interpreted languages (Python, Node.js)

Full Rebuild:

• Complete Docker build cycle
• Required when dependencies change
• Slower but ensures clean state

3. How do resource dependencies work?

resource_deps ensures resources start in order:

• Dependent resource waits for dependencies to be "ready"
• Ready = Kubernetes reports resource as available
• Prevents startup race conditions

4. Best practices for Tiltfile organization?

1. Group related resources with labels
2. Use extensions for common patterns
3. Configure ignore to skip unnecessary rebuilds
4. Use live_update for fast iteration
5. Set appropriate trigger_mode for expensive operations
6. Document custom configurations with comments