Attempt to randomize port on startup if default is unavailable
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Description
When switching between tilt projects that contain tilt wrappers (e.g. make tilt) I'll often hit issues with port allocation issues. My options tend to be:
- stop one project (which could be costly to start back up)
- fall back to running tilt directly (could need to run several setup tasks directly)
- assign tilt ports in each project (or at least allow setting them via ENV_VAR)
I'd like for tilt to have a (optional?) method to randomize port allocation if the default port is in use.
An alternative I've thought about is a tilt daemon/manager that is project context aware. Tilt could host its web-ui on the same port but provide subpaths for components running under different Tiltfile contexts (e.g. localhost:10350/project1, localhost:10350/project2).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or tests. Start by tracing Tilt startup's web-UI port allocation and checking behavior when the default port is occupied. Done would require a clearly defined optional fallback policy for port selection, including how users configure it and how existing project workflows behave.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100