tiny-pilot / tiny-pilot/tinypilot
Specify HTTP proxy for install
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.5k
- Forks
- 291
- PR merge metrics
- No merged PRs in 30d
Description
For customers that keep TinyPilot on a restricted network, they can't update through the web UI.
It would be helpful in these situations to allow the user to specify an HTTP proxy on the update dialog so that TinyPilot does all network requests through the HTTP proxy instead of trying to access the Internet directly.
We should be able to set the HTTP_PROXY environment variable, but the tricky part is that we call sudo at least twice (a, b) in the update path, which would drop environment variables. We could preserve the variable with sudo --preserve-env=HTTP_PROXY, but maybe there's another solution.
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
Read app/update/launcher.py at the linked sudo call and get-tinypilot.sh at its linked sudo call to trace the update path. Determine how the update dialog can pass an HTTP proxy through those commands, then verify that web UI updates make their network requests through the configured proxy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, shell
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100