From ac4b46ba7dc2cb9be654a2e903f526f5b548fc01 Mon Sep 17 00:00:00 2001 From: DrMelone <27028174+Classic298@users.noreply.github.com> Date: Sat, 20 Dec 2025 20:19:55 +0100 Subject: [PATCH] rem remnance --- .../advanced-topics/https-encryption.md | 10 +++++++--- docs/getting-started/advanced-topics/logging.md | 5 ----- 2 files changed, 7 insertions(+), 8 deletions(-) diff --git a/docs/getting-started/advanced-topics/https-encryption.md b/docs/getting-started/advanced-topics/https-encryption.md index 89311741..037840ed 100644 --- a/docs/getting-started/advanced-topics/https-encryption.md +++ b/docs/getting-started/advanced-topics/https-encryption.md @@ -45,10 +45,14 @@ The best HTTPS solution depends on your existing infrastructure and technical ex - **Scalability and Performance:** Consider the performance and scalability needs of your Open WebUI instance when choosing a solution, especially for high-traffic deployments. - **Cost:** Some solutions (like cloud load balancers or Cloudflare's paid plans) may have associated costs. Let's Encrypt and many reverse proxies are free and open-source. -## 📚 Explore Deployment Tutorials for Step-by-Step Guides +## 📚 Explore HTTPS Tutorials -For detailed, practical instructions and community-contributed tutorials on setting up HTTPS encryption with various solutions, please visit the **[Deployment Tutorials](../../../tutorials/deployment/)** section. +We have dedicated step-by-step guides for setting up reverse proxies with HTTPS: -These tutorials often provide specific, step-by-step guides for different environments and HTTPS solutions, making the process easier to follow. +* **[Nginx](../../../tutorials/https/nginx.md)**: Industry-standard high-performance server. +* **[Caddy](../../../tutorials/https/caddy.md)**: Easiest setup with automatic HTTPS. +* **[HAProxy](../../../tutorials/https/haproxy.md)**: Robust load balancer and proxy. + +These tutorials provide specific configuration examples to get your secure Open WebUI instance running quickly. By implementing HTTPS, you significantly enhance the security and functionality of your Open WebUI instance, ensuring a safer and more feature-rich experience for yourself and your users. diff --git a/docs/getting-started/advanced-topics/logging.md b/docs/getting-started/advanced-topics/logging.md index ab818de1..ace9159c 100644 --- a/docs/getting-started/advanced-topics/logging.md +++ b/docs/getting-started/advanced-topics/logging.md @@ -85,10 +85,5 @@ Setting `GLOBAL_LOG_LEVEL` configures the root logger in Python, affecting all l **Impact:** Setting `GLOBAL_LOG_LEVEL` to `DEBUG` will produce the most verbose logs, including detailed information that is helpful for development and troubleshooting. For production environments, `INFO` or `WARNING` might be more appropriate to reduce log volume. -:::note - -**Important Note:** Unlike `GLOBAL_LOG_LEVEL`, these app-specific variables might not affect logging from *all* third-party modules. They primarily control logging within Open WebUI's codebase. - -::: By understanding and utilizing these logging mechanisms, you can effectively monitor, debug, and gain insights into your Open WebUI instance.