|
|
|
@ -106,7 +106,7 @@
|
|
|
|
|
## Note that if the DB already has WAL enabled, you will also need to disable WAL in the DB,
|
|
|
|
|
## this setting only prevents vaultwarden from automatically enabling it on start.
|
|
|
|
|
## Please read project wiki page about this setting first before changing the value as it can
|
|
|
|
|
## cause performance degradation or might render the service unable to start.
|
|
|
|
|
## cause performance degradation or might render the service unable to start.
|
|
|
|
|
# ENABLE_DB_WAL=true
|
|
|
|
|
|
|
|
|
|
## Database connection retries
|
|
|
|
@ -252,7 +252,7 @@
|
|
|
|
|
## You can disable this, so that only the current TOTP Code is allowed.
|
|
|
|
|
## Keep in mind that when a sever drifts out of time, valid codes could be marked as invalid.
|
|
|
|
|
## In any case, if a code has been used it can not be used again, also codes which predates it will be invalid.
|
|
|
|
|
# AUTHENTICATOR_DISABLE_TIME_DRIFT = false
|
|
|
|
|
# AUTHENTICATOR_DISABLE_TIME_DRIFT=false
|
|
|
|
|
|
|
|
|
|
## Rocket specific settings, check Rocket documentation to learn more
|
|
|
|
|
# ROCKET_ENV=staging
|
|
|
|
|