vw_small

Hardened fork of Vaultwarden (https://github.com/dani-garcia/vaultwarden) with fewer features.
git clone https://git.philomathiclife.com/repos/vw_small
Log | Files | Refs | README

commit 21325b7523a68ab3ae8d435ab5b73176db6155ff
parent 874f5c34bdb2272f3cac1ceef13edea22b6e263d
Author: Daniel GarcĂ­a <dani-garcia@users.noreply.github.com>
Date:   Sat, 27 Apr 2019 20:14:37 +0200

Updated .env template

Diffstat:
M.env.template | 13+++++++------
1 file changed, 7 insertions(+), 6 deletions(-)

diff --git a/.env.template b/.env.template @@ -35,7 +35,7 @@ ## Enable extended logging ## This shows timestamps and allows logging to file and to syslog ### To enable logging to file, use the LOG_FILE env variable -### To enable syslog, you need to compile with `cargo build --features=enable_syslog' +### To enable syslog, use the USE_SYSLOG env variable # EXTENDED_LOGGING=true ## Logging to file @@ -43,6 +43,11 @@ ## It's recommended to also set 'ROCKET_CLI_COLORS=off' # LOG_FILE=/path/to/log +## Logging to Syslog +## This requires extended logging +## It's recommended to also set 'ROCKET_CLI_COLORS=off' +# USE_SYSLOG=false + ## Log level ## Change the verbosity of the log output ## Valid values are "trace", "debug", "info", "warn", "error" and "off" @@ -113,17 +118,13 @@ # YUBICO_SERVER=http://yourdomain.com/wsapi/2.0/verify ## Duo Settings -## You need to configure all options to enable Duo support +## You need to configure all options to enable global Duo support, otherwise users would need to configure it themselves ## Create an account and protect an application as mentioned in this link (only the first step, not the rest): ## https://help.bitwarden.com/article/setup-two-step-login-duo/#create-a-duo-security-account ## Then set the following options, based on the values obtained from the last step: # DUO_IKEY=<Integration Key> # DUO_SKEY=<Secret Key> # DUO_HOST=<API Hostname> -## The Aplication Key needs to be randomly generated. Recommended at least 40 characters in base64. -## Example command to generate it: 'openssl rand -base64 48' -## Note that this shouldn't change between runs. -# DUO_AKEY=<Application Key> ## After that, you should be able to follow the rest of the guide linked above, ## ignoring the fields that ask for the values that you already configured beforehand.