[PR #1377] [CLOSED] docs: add ZeroSignal tutorial under LLM providers #1344

Closed
opened 2026-10-18 14:19:01 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/open-webui/docs/pull/1377
Author: @johnmizz
Created: 9/3/2026
Status: ❌ Closed

Base: main ← Head: zerosignal-tutorial


📝 Commits (1)

  • 86a8130 docs: add ZeroSignal LLM provider tutorial

📊 Changes

1 file changed (+92 additions, -0 deletions)

View changed files

➕ docs/tutorials/integrations/llm-providers/zerosignal.md (+92 -0)

📄 Description

Summary

Adds a community tutorial at docs/tutorials/integrations/llm-providers/zerosignal.md for connecting Open WebUI to ZeroSignal, a private pay-per-use inference network reached through its local zs-proxy daemon (an OpenAI-compatible endpoint on port 9376 with no API key).

The page follows the existing provider tutorials in that folder (same community-contribution banner as ipex_llm.md) and is a concrete setup walkthrough: prerequisites, the Docker networking change users trip over (host.docker.internal plus binding the proxy off loopback, with the exposure warning), the OpenAI API connection form values, filtering the model list, and a troubleshooting table.

None.

Checklist

  • I have reviewed the relevant documentation and matched the existing style.
  • This PR meets Open WebUI's contribution standards: it is accurate, relevant to users, narrowly scoped, maintainable, and not promotional content, advertising, lead generation, SEO placement, or a request to list a product, service, provider, integration, gateway, tool, or company primarily for visibility.
  • I understand that PRs that do not meet these standards may be closed without review and will not be merged. Repeated, low-quality, off-topic, promotional, or intentionally misleading submissions may result in the contributor being blocked from future participation in Open WebUI repositories.

Notes for reviewers

This is a provider setup tutorial in the community llm-providers folder, written from a working install: the connection values and the Docker steps were checked against zs-proxy v0.21.0 and Open WebUI's OpenAI API connection form. No claims about Open WebUI internals; everything routes through the standard OpenAI connection.

🤖 Generated with Claude Code


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/open-webui/docs/pull/1377 **Author:** [@johnmizz](https://github.com/johnmizz) **Created:** 9/3/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `zerosignal-tutorial` --- ### 📝 Commits (1) - [`86a8130`](https://github.com/open-webui/docs/commit/86a81307b98f83842a76a6e28e956ac04aaaa2b0) docs: add ZeroSignal LLM provider tutorial ### 📊 Changes **1 file changed** (+92 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `docs/tutorials/integrations/llm-providers/zerosignal.md` (+92 -0) </details> ### 📄 Description ## Summary Adds a community tutorial at `docs/tutorials/integrations/llm-providers/zerosignal.md` for connecting Open WebUI to [ZeroSignal](https://zerosignal.ai), a private pay-per-use inference network reached through its local `zs-proxy` daemon (an OpenAI-compatible endpoint on port 9376 with no API key). The page follows the existing provider tutorials in that folder (same community-contribution banner as `ipex_llm.md`) and is a concrete setup walkthrough: prerequisites, the Docker networking change users trip over (`host.docker.internal` plus binding the proxy off loopback, with the exposure warning), the OpenAI API connection form values, filtering the model list, and a troubleshooting table. ## Related issue or discussion None. ## Checklist - [x] I have reviewed the relevant documentation and matched the existing style. - [x] This PR meets Open WebUI's contribution standards: it is accurate, relevant to users, narrowly scoped, maintainable, and not promotional content, advertising, lead generation, SEO placement, or a request to list a product, service, provider, integration, gateway, tool, or company primarily for visibility. - [x] I understand that PRs that do not meet these standards may be closed without review and will not be merged. Repeated, low-quality, off-topic, promotional, or intentionally misleading submissions may result in the contributor being blocked from future participation in Open WebUI repositories. ## Notes for reviewers This is a provider setup tutorial in the community `llm-providers` folder, written from a working install: the connection values and the Docker steps were checked against zs-proxy v0.21.0 and Open WebUI's OpenAI API connection form. No claims about Open WebUI internals; everything routes through the standard OpenAI connection. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-18 14:19:01 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
open-webui/docs#1344
No description provided.