[GH-ISSUE #13108] feat: Make connection to Pipeline service automatic with env variable #32341

Closed
opened 2026-04-25 06:14:17 -05:00 by GiteaMirror · 3 comments
Owner

Originally created by @mikkeschiren on GitHub (Apr 21, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/13108

Check Existing Issues

  • I have searched the existing issues and discussions.

Problem Description

Every time I start developing with Open Web UI I need to manually set the connection to the pipeline service (in my case a docker container service).

Desired Solution you'd like

As the pipeline service should be something that most setups needs, It should be nice if the connection to the pipeline service could be automated. Like with a ENV variable, so if that variable is set, the connection to the pipeline services is activated on startup.

PIPELINE_SERVICE=http://host.docker.internal:9099
PIPELINE_AUTH_TOKEN=0p3n-w3bu!

So if the variable PIPELINE_SERVICE is set, it should contect to it on startup, with provided token, without the need for activating through UI.

Alternatives Considered

No response

Additional Context

No response

Originally created by @mikkeschiren on GitHub (Apr 21, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/13108 ### Check Existing Issues - [x] I have searched the existing issues and discussions. ### Problem Description Every time I start developing with Open Web UI I need to manually set the connection to the pipeline service (in my case a docker container service). ### Desired Solution you'd like As the pipeline service should be something that most setups needs, It should be nice if the connection to the pipeline service could be automated. Like with a ENV variable, so if that variable is set, the connection to the pipeline services is activated on startup. PIPELINE_SERVICE=http://host.docker.internal:9099 PIPELINE_AUTH_TOKEN=0p3n-w3bu! So if the variable PIPELINE_SERVICE is set, it should contect to it on startup, with provided token, without the need for activating through UI. ### Alternatives Considered _No response_ ### Additional Context _No response_
Author
Owner

@tjbck commented on GitHub (Apr 21, 2025):

Supported already.

<!-- gh-comment-id:2818487515 --> @tjbck commented on GitHub (Apr 21, 2025): Supported already.
Author
Owner

@mikkeschiren commented on GitHub (Apr 21, 2025):

Sorry - but where is that documented?

<!-- gh-comment-id:2819065794 --> @mikkeschiren commented on GitHub (Apr 21, 2025): Sorry - but where is that documented?
Author
Owner

@mikkeschiren commented on GitHub (Apr 21, 2025):

Ok, I found it. Pipelines is connected wirth env variable OPENAI_API_BASE_URLS, just add pipeline containers address together with the one to https://api.openai.com/v1 - like:

OPENAI_API_BASE_URLS=http://pipelines:9099;https://api.openai.com/v1

And the key like:

OPENAI_API_KEY=0p3n-w3bu!
<!-- gh-comment-id:2819120847 --> @mikkeschiren commented on GitHub (Apr 21, 2025): Ok, I found it. Pipelines is connected wirth env variable `OPENAI_API_BASE_URLS`, just add pipeline containers address together with the one to https://api.openai.com/v1 - like: ``` OPENAI_API_BASE_URLS=http://pipelines:9099;https://api.openai.com/v1 ``` And the key like: ``` OPENAI_API_KEY=0p3n-w3bu! ```
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#32341