docs: backups page says what cache/ is, and gains a Restoring section - #1379
Open
spelingbee wants to merge 1 commit into
Open
docs: backups page says what cache/ is, and gains a Restoring section#1379spelingbee wants to merge 1 commit into
spelingbee wants to merge 1 commit into
Conversation
## Summary Two additions to the backups page. The files table now says what `cache/` is (downloaded embedding and speech models, re-downloaded on demand, safe to exclude, and why two of the three example scripts exclude it: on a fresh instance it was 1.1 GB against about a megabyte of user data, and it contains symlinks). And a short Restoring section, since the page covers taking a backup and stops there: stop the stack, put the data directory back, start it, and make sure `webui.db-wal` / `webui.db-shm` travel with `webui.db` if files were copied individually. ## Related issue or discussion open-webui#1378 ## 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 Measured on v0.11.1 with the default SQLite setup, one account and one chat: `du` of the data directory was 1.1G, of which `cache/` was 1.1G, `webui.db` 632K, `webui.db-wal` 160K, `vector_db` 184K. The restore sequence was tested by restoring the directory into a fresh stack, with and without `cache/`. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0193orVXP78niTTs6AzLThHK
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Two additions to the backups page. The files table now says what
cache/is (downloaded embedding and speech models, re-downloaded on demand, safe to exclude, and why two of the three example scripts exclude it: on a fresh instance it was 1.1 GB against about a megabyte of user data, and it contains symlinks). And a short Restoring section, since the page covers taking a backup and stops there: stop the stack, put the data directory back, start it, and make surewebui.db-wal/webui.db-shmtravel withwebui.dbif files were copied individually.Related issue or discussion
#1378
Checklist
Notes for reviewers
Measured on v0.11.1 with the default SQLite setup, one account and one chat:
duof the data directory was 1.1G, of whichcache/was 1.1G,webui.db632K,webui.db-wal160K,vector_db184K. The restore sequence was tested by restoring the directory into a fresh stack, with and withoutcache/.Closes #1378.