Run Tilt UI behind a reverse proxy
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Description
Describe the Feature You Want
I want to run Tilt behind a reverse proxy, for example, having it run at https://dev.example.com/tilt/
Current Behavior
At the moment this is not possible because:
- Static assets are always fetched at
/static(i.e., not at/tilt/static) - Navigation within the UI rewrites the browser's URL (i.e.,
/r/service/overviewinstead of/tilt/r/service/overview)
Why Do You Want This?
My application runs many services, and I'm using Tilt to orchestrate them. I'm exposing the dev environment from a remote virtual machine behind a reverse-proxy. It would be very helpful to have Tilt accessible from the same reverse-proxy (e.g., at /tilt) so that we can inspect the logs.
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
No files or tests are named in the issue. Start by tracing how the UI builds static-asset URLs and navigation URLs, then determine where a configured /tilt base path would apply. Done means Tilt can be served behind a reverse proxy at a path such as /tilt/, with assets and navigation retaining that prefix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100