[0.1.7] [Windows 11 x64] Support custom PyPI/package mirror for Open Terminal installation
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- python, typescript
- Domain
- tooling
Research direction
Start from the "Install" button handler for Open Terminal in the Tether UI and follow it to the code that shells out to pip, noting how the subprocess environment is built. Then look at how settings are defined and persisted so a new package-mirror/proxy URL field can be added and read at install time; decide whether to pass PIP_INDEX_URL/proxy env vars or write a pip config. Done means a user can set a mirror in settings and the Install button succeeds without external access, ideally checked by a manual run on Windows behind a firewall.
Written by the indexing model from the issue text.
Description
Version
0.1.7
Platform
Windows 11 x64
Description
I am using Tether in a corporate environment where all external internet access is blocked, and all packages must be pulled from an internal Azure Artifacts mirror.
Currently, the "Install" button in the Tether UI for Open Terminal fails because it defaults to standard external repositories and does not appear to respect system-level pip configurations (pip.ini/pip.conf) or environment variables for package mirrors.
Proposed Solution:
Please add an option in Tether settings to define a custom package source URL or proxy configuration for the Open Terminal installation process. This would allow users in restricted environments to configure Tether to point to their internal corporate mirrors.
Context:
Environment: Windows (behind corporate firewall).
Desired Workflow: Tether's "Install" button should support the same network proxy/mirror settings so it can provision Open Terminal without requiring manual CLI intervention.
Steps to reproduce
No response
Additional context
No response
- Dominant language
- TypeScript
- Stars
- 130
- Forks
- 8
- Avg merge
- 1m
- Merged PRs (30d)
- 15
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing 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.
More from open-webui/tether
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
open-webui/tether#52 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 28/100
open-webui/tether#50 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
open-webui/tether#49 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 12/100
open-webui/tether#48 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
open-webui/tether#44 ·
Maintainers usually reply within 1 day
All issues in open-webui/tether
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
voidzero-dev/void#835 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
AykutSarac/jsoncrack.com#616 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
melgarafael/DeskcommCRM#4679 ·
Maintainers usually reply within 1 day
-
enhancement size:medium
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day