tilt-dev / tilt-dev/tilt.build

Add guidance for optimized live_update workflow with more frameworks

Open
#809 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
24
Forks
68
PR merge metrics
No merged PRs in 30d

Description

This was prompted by a user request to add a Python + fastapi example.

There's generally many popular frameworks for any given language, and it's likely impractical to maintain full examples for each. However, we could probably offer some guidance around common options/flags (e.g. most Python frameworks can run in a dev server mode that automatically picks up changes to code) for the most popular frameworks.

If there's a framework (not necessarily Python!) you're struggling to optimize your Tiltfile + live_update for, add a comment here with some details!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the existing live_update workflow guidance and review how a Python/FastAPI development server handles code changes. Define practical options or flags for common frameworks, include the requested FastAPI example, and consider the community framework cases described in the issue. Done means the documentation gives useful optimization guidance without requiring a full example for every framework.

Written by the indexing model from the issue text.

Assessment

Tech stack
fastapi, python
Domain
documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.