Typo correction

Adam Berry 2023-09-06 18:26:16 +01:00
parent 9120530dc8
commit 94bd16bd5a
1 changed files with 1 additions and 1 deletions

@ -62,7 +62,7 @@ While launching, Vaultwarden checks for the existence of a file called `.env` (i
<br> <br>
## Can i run Vaultwarden as an Azure WebApp ## Can i run Vaultwarden as an Azure WebApp
Unfortunately Azure WebApp's uses CIFS/Samba as there volume storage which does not support locking. This causes issues with the SQLite database file. Unfortunately Azure WebApp's uses CIFS/Samba as their volume storage which does not support locking. This causes issues with the SQLite database file.
There are two ways to solve this. There are two ways to solve this.
1. Do not use SQLite, but MariaDB/MySQL or Posgresql as the database backend. 1. Do not use SQLite, but MariaDB/MySQL or Posgresql as the database backend.
2. Try to disable WAL using the `ENABLE_DB_WAL` environment variable by setting it's value to `false`. This needs to be done on a new file, so you need to remove the previously created `db.sqlite3` file and restart the Vaultwarden app again. 2. Try to disable WAL using the `ENABLE_DB_WAL` environment variable by setting it's value to `false`. This needs to be done on a new file, so you need to remove the previously created `db.sqlite3` file and restart the Vaultwarden app again.