open-webui / open-webui/terminals
FR: `TERMINALS_NETWORK` tiering support, and host network support
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 108
- Forks
- 23
- Avg merge
- 12h 8m
- Merged PRs (30d)
- 1
Description
It would be great if I can assign certain users' terminals to a particular docker network, so that I can assign who gets external network access. An example:
Admin/trusted users: terminal containers connect to priviledged bridge with internet and physical network access; or connect to a host network directly without a bridge
Normal users: on a bridge with internet access only (additional firewall rules), no local physical network access
Restricted users: on a pure internal bridge, no external net access
Contributor guide
No contributing guide indexed for this repository
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
Start by tracing how TERMINALS_NETWORK is currently read and how terminal containers are created and attached to Docker networks. Define how trusted, normal, and restricted users are assigned their respective network modes or bridges, then verify that external and physical-network access matches each tier.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- infrastructure, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100