centersl/open-webui-docs
1
0
Fork 0
mirror of https://github.com/open-webui/docs.git synced 2026-03-27 13:28:37 +07:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #947 from Classic298/dev

Browse Source
This commit is contained in:
Classic298
2026-01-03 00:11:58 +01:00
committed by GitHub
parent 448a3f1649 3705b19505
commit 7fed0f9301
2 changed files with 21 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/getting-started/env-configuration.mdx
View File

@@ -5382,6 +5382,14 @@ Ensure the database password is kept secure, as it is needed to decrypt and acce
:::
:::warning Migrating Existing Data to SQLCipher
**Open WebUI does not support automatic migration from an unencrypted SQLite database to an encrypted SQLCipher database.** If you enable SQLCipher on an existing installation, the application will fail to read your existing unencrypted data.
To use SQLCipher with existing data, you must either start fresh (with users exporting/re-importing chats), manually migrate the database using external SQLite/SQLCipher tools, use filesystem-level encryption (LUKS/BitLocker) instead, or switch to PostgreSQL.
:::
#### `DATABASE_SCHEMA`
- Type: `str`

13
docs/tutorials/tips/sqlite-database.md
View File

@@ -764,6 +764,19 @@ When these are set and a full `DATABASE_URL` is **not** explicitly defined, Open
:::
:::warning Migrating Existing Data to SQLCipher
**Open WebUI does not support automatic migration from an unencrypted SQLite database to an encrypted SQLCipher database.** If you enable SQLCipher on an existing installation, the application will fail to read your existing unencrypted data.
To use SQLCipher with existing data, you must either:
1. **Start fresh** - Enable SQLCipher on a new installation and have users export/re-import their chats manually
2. **Manual database migration** - Use external SQLite/SQLCipher tools to export data from the unencrypted database and import it into a new encrypted database (advanced users only)
3. **Use filesystem-level encryption** - Consider alternatives like LUKS (Linux) or BitLocker (Windows) for at-rest encryption without database-level changes
4. **Switch to PostgreSQL** - For multi-user deployments, PostgreSQL with TLS provides encryption in transit and can be combined with encrypted storage
:::
### Related Database Environment Variables
| Variable | Default | Description |