khanh.pndc/open-webui-docs
1
0
Fork 0
mirror of https://github.com/open-webui/docs.git synced 2026-01-04 02:36:55 +07:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #893 from alicanyuksel/update-docs

Browse Source 
Lgtm
This commit is contained in:
Classic298
2025-12-19 09:18:48 +01:00
committed by GitHub
parent 4142ff92fa 6cdbfdac3b
commit 7cc64e2e76
3 changed files with 50 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/getting-started/quick-start/tab-docker/ManualDocker.md
View File

@@ -18,6 +18,14 @@ For environments with limited storage or bandwidth, Open WebUI offers slim image
docker pull ghcr.io/open-webui/open-webui:main-slim
```
### Specific release version
You can also pull a specific Open WebUI release version directly by using a versioned image tag. This is recommended for production environments to ensure stable and reproducible deployments.
```bash
docker pull ghcr.io/open-webui/open-webui:v0.6.41
```
## Step 2: Run the Container
Run the container with default settings. This command includes a volume mapping to ensure persistent data storage.

26
docs/getting-started/updating.mdx
View File

@@ -57,6 +57,32 @@ Status: Downloaded newer image for ghcr.io/open-webui/open-webui:main
Your chat histories, settings, and uploaded files are stored in a Docker volume named `open-webui`. Pulling a new image does **not** affect this data. The volume persists independently of the container.
:::
### (Optional) Using image tags in production
Open WebUI provides multiple Docker image tags depending on how you want to manage updates.
If you want to always run the latest version of Open WebUI, you can use the `:main`, `:cuda`, or `:ollama` image tags, depending on your setup.
Examples (latest version tags):
```
ghcr.io/open-webui/open-webui:main
ghcr.io/open-webui/open-webui:cuda
ghcr.io/open-webui/open-webui:ollama
```
For `production environments` where stability and reproducibility are important, it is recommended to pin a specific release version instead of using these floating tags.
Versioned images follow this format:
```
ghcr.io/open-webui/open-webui:<RELEASE_VERSION>-<TYPE>
```
Examples (pinned versions — replace with the release version you want to use):
```
ghcr.io/open-webui/open-webui:v0.6.41
ghcr.io/open-webui/open-webui:v0.6.41-cuda
ghcr.io/open-webui/open-webui:v0.6.41-ollama
```
### Step 3: Start Container with Updated Image
Recreate the container using the new image while mounting your existing data volume.

16
docs/intro.mdx
View File

@@ -89,6 +89,22 @@ Both commands facilitate a built-in, hassle-free installation of both Open WebUI
After installation, you can access Open WebUI at [http://localhost:3000](http://localhost:3000). Enjoy! 😄
### Using image tags in production
If you want to always run the latest version of Open WebUI, you can use the `:main`, `:cuda`, or `:ollama` image tags, depending on your setup, as shown in the examples above.
For `production environments` where stability and reproducibility are important, it is recommended to pin a specific release version instead of using these floating tags. Versioned images follow this format:
```
ghcr.io/open-webui/open-webui:<RELEASE_VERSION>-<TYPE>
```
Examples (pinned versions for illustration purposes only):
```
ghcr.io/open-webui/open-webui:v0.6.41
ghcr.io/open-webui/open-webui:v0.6.41-ollama
ghcr.io/open-webui/open-webui:v0.6.41-cuda
```
### Using the Dev Branch 🌙
:::warning