Merge pull request #786 from open-webui/main

This commit is contained in:
Classic298
2025-10-30 23:18:26 +01:00
committed by GitHub
6 changed files with 43 additions and 21 deletions

View File

@@ -11,7 +11,7 @@ import { TopBanners } from "@site/src/components/TopBanners";
**A:** You can customize the theme, logo, and branding with our **[Enterprise License](https://docs.openwebui.com/enterprise)**, which unlocks exclusive enterprise features.
For more details on enterprise solutions and branding customizations, please contact our sales team at: 📧 **sales@openwebui.com**
For more details on enterprise solutions and branding customizations, [click here](https://docs.openwebui.com/enterprise).
### **Q: Why am I asked to sign up? Where are my data being sent to?**

View File

@@ -192,7 +192,7 @@ There are several example configurations that are provided in this page.
:::danger
Incorrect configuration can allow users to authenticate as any user on your Open WebUI instance.
Make sure to allow only the authenticating proxy access to Open WebUI, such as setting `HOST=127.0.0.1` to only listen on the loopback interface.
Make sure to allow only the authenticating proxy access to Open WebUI, such as by not opening any ports directly to the container, or by setting `HOST=127.0.0.1` so that it only listens on the loopback interface.
:::
@@ -251,7 +251,6 @@ services:
volumes:
- open-webui:/app/backend/data
environment:
- HOST=127.0.0.1
- WEBUI_AUTH_TRUSTED_EMAIL_HEADER=Tailscale-User-Login
- WEBUI_AUTH_TRUSTED_NAME_HEADER=Tailscale-User-Name
restart: unless-stopped
@@ -302,7 +301,6 @@ services:
volumes:
- open-webui:/app/backend/data
environment:
- HOST=127.0.0.1
- WEBUI_AUTH_TRUSTED_EMAIL_HEADER=Cf-Access-Authenticated-User-Email
restart: unless-stopped
cloudflared:
@@ -331,7 +329,6 @@ services:
volumes:
- open-webui:/app/backend/data
environment:
- 'HOST=127.0.0.1'
- 'WEBUI_AUTH_TRUSTED_EMAIL_HEADER=X-Forwarded-Email'
- 'WEBUI_AUTH_TRUSTED_NAME_HEADER=X-Forwarded-User'
restart: unless-stopped

View File

@@ -162,6 +162,27 @@ VS Code's integrated terminal feature makes managing multiple terminals incredib
🎉 **Congratulations!** If you have followed all the steps, you should now have both the frontend and backend development servers running locally. Go back to your browser tab where you accessed the frontend (usually [http://localhost:5173](http://localhost:5173)). **Refresh the page.** You should now see the full Open WebUI application running in your browser, connected to your local backend!
## Testing From Another Device (Phone, Tablet, etc.)
Want to open your dev instance from your phone or another computer on the same Wi-Fi?
1. Find your dev-machines LAN IP, e.g. `192.168.1.42`.
2. **Frontend only (quick check):**
- Keep the backend on `localhost`.
- From your phone browse to `http://192.168.1.42:5173`.
3. **Full stack (frontend + backend):**
- In `backend/dev.sh` **add your LAN address to the CORS list**, e.g.
```bash
export CORS_ALLOW_ORIGIN="http://localhost:5173;http://localhost:8080;http://192.168.1.42:5173"
```
- Restart the backend (`sh dev.sh`).
- From your phone browse to `http://192.168.1.42:5173`.
- All API calls will now be allowed from that origin.
> **Security note:** The wildcard `"*"` works too, but do **not** ship that to production.
## Troubleshooting Common Issues
Here are solutions to some common problems you might encounter during setup or development:

View File

@@ -172,7 +172,7 @@ We believe open ecosystems work best for users, contributors, and the future of
### **7. What if I want to white-label or deeply customize Open WebUI for my enterprise?**
Contact us! We offer **proprietary and enterprise licenses** allowing fully custom branding, priority support, feature requests, and more. Email [sales@openwebui.com](mailto:sales@openwebui.com) for details.
Contact us! We offer **proprietary and enterprise licenses** allowing fully custom branding, priority support, feature requests, and more. [Click here](https://docs.openwebui.com/enterprise) for details.
### **8. What if I already deployed Open WebUI before v0.6.6?**
@@ -234,7 +234,7 @@ Display this message—prominently—in the About section, landing page, or equi
If you are a business that needs private or custom branding, advanced white-label deployments, or tailored features for mission-critical use cases, **we offer proprietary and enterprise licenses**. Well work with you to ensure your needs and your branding are fully addressed, with a world-class support and engineering team backing your deployment.
**Contact [sales@openwebui.com](mailto:sales@openwebui.com) for more information about commercial options.**
**[Click here](https://docs.openwebui.com/enterprise) for more information about commercial options.**
---

View File

@@ -77,32 +77,20 @@ const config: Config = {
srcDark: "images/logo-dark.png",
},
items: [
// {
// type: "docSidebar",
// position: "left",
// sidebarId: "pipelines",
// label: "Pipelines",
// },
// {
// type: "docSidebar",
// sidebarId: "blog",
// position: "left",
// label: "Blog",
// },
{
to: "blog",
label: "Blog",
position: "left",
},
{
label: "GitHub",
href: "https://github.com/open-webui/open-webui",
position: "right",
className: "header-github-link",
"aria-label": "GitHub repository",
},
{
label: "Discord",
href: "https://discord.com/invite/5rJgQTnV4s",
position: "right",
className: "header-discord-link",

View File

@@ -637,6 +637,22 @@ div.special_table + table tr:nth-child(even) {
min-height: 100vh;
}
.header-github-link,
.header-discord-link {
gap: 0.25rem;
}
@media screen and (width >= 997px) {
.header-github-link,
.header-discord-link {
font-size: 0;
}
}
.header-discord-link {
margin-right: 16px;
}
.header-github-link::before {
content: "";
width: 24px;