vaultwarden
/
vaultwarden-alternativa-bitwarden
mirror of https://github.com/dani-garcia/vaultwarden.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

The way to properly set log level was changed.

Ayitaka 2019-08-12 06:02:31 -07:00
parent 6195698f90
commit 0d38331b25
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Logging.md

@ -13,11 +13,13 @@ Note that if you're using the docker image, you'll most likely want to use a fil
# Change the log level
To reduce the amount of log messages, you can set the log level to 'critical' (default is 'normal') and disable the extended logging (enabled by default). The [Log level](https://api.rocket.rs/v0.3/rocket/config/enum.LoggingLevel.html) can be adjusted with the environment variable `ROCKET_LOG`. Extended logging can be deactivated by setting the environment variable `EXTENDED_LOGGING` to 'false'. Be advised, disabling `EXTENDED_LOGGING` will stop the log file from being written to.
To reduce the amount of log messages, you can set the log level to 'warn' (default is 'info'). The [Log level](https://docs.rs/log/0.4.7/log/enum.Level.html#variants) can be adjusted with the environment variable `LOG_LEVEL` while also setting `EXTENDED_LOGGING=true`. NOTE: Using the log level "warn" still allows [Fail2Ban](https://github.com/dani-garcia/bitwarden_rs/wiki/Fail2Ban-Setup) to work properly.
`LOG_LEVEL` options are: "trace", "debug", "info", "warn", "error" or "off".
```sh
docker run -d --name bitwarden \
...
-e ROCKET_LOG=critical -e EXTENDED_LOGGING=false \
-e LOG_LEVEL=warn -e EXTENDED_LOGGING=true \
...
```