OpenWebUI/docs
1
0
Fork 0
mirror of https://github.com/open-webui/docs synced 2025-06-16 11:28:36 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Tips coming from Git

Browse Source
This commit is contained in:
Valentino Stillhardt 2024-06-12 10:03:12 -03:00 committed by GitHub
parent 28ab1ae980
commit 70ed3d891d
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 21 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
docs/migration.mdx
View File

@ -69,6 +69,8 @@ docker volume rm ollama-webui
For example, for local installation it would be `docker run -d -p 3000:8080 --add-host=host.docker.internal:host-gateway -v open-webui:/app/backend/data --name open-webui --restart always ghcr.io/open-webui/open-webui:main`. For other installation commands, check the relevant parts of this README document. For example, for local installation it would be `docker run -d -p 3000:8080 --add-host=host.docker.internal:host-gateway -v open-webui:/app/backend/data --name open-webui --restart always ghcr.io/open-webui/open-webui:main`. For other installation commands, check the relevant parts of this README document.
## Updating to Open WebUI while keeping your data
If you want to update to the new image migrating all your previous settings like conversations, prompts, documents, etc. you can perform the following steps: If you want to update to the new image migrating all your previous settings like conversations, prompts, documents, etc. you can perform the following steps:
```bash ```bash
@ -85,3 +87,22 @@ Once you verify that all the data has been migrated you can erase the old volume
```bash ```bash
docker volume rm ollama-webui docker volume rm ollama-webui
``` ```
### Coming from a local Git repository
If you came from a git installation where you used `docker compose up` in the project directory, your volumes will be prefixed with the folder name.
Therefore, if your OpenWebUI path was: `/home/myserver/ollama-webui/`, the volumes would be named "ollama-webui_open-webui" and "ollama-webui_ollama".
To copy the contents over to a conventional docker installation, you may run the same migration commands, but replacing them with the prefixed volume names and creating an additional volume for ollama. In our particular case, the commands would be:
```bash
docker rm -f ollama-webui
docker pull ghcr.io/open-webui/open-webui:main
docker pull ghcr.io/open-webui/open-webui:ollama
docker volume create --name open-webui
docker volume create --name ollama
docker run --rm -v ollama-webui_open-webui:/from -v open-webui:/to alpine ash -c "cd /from ; cp -av . /to"
docker run --rm -v ollama-webui_ollama:/from -v ollama:/to alpine ash -c "cd /from ; cp -av . /to"
```
Then, start both containers as usual, as described in the Getting started guide.
Once you verify that all the data has been migrated you can erase the old volume using the command `docker volume rm` mentioned above.