diff options
| author | dobunzli <[email protected]> | 2018-09-14 22:39:58 +0200 |
|---|---|---|
| committer | GitHub <[email protected]> | 2018-09-14 22:39:58 +0200 |
| commit | eb61425da5bd1be8e386cc67da15655c9462fbd1 (patch) | |
| tree | 3a3a70d05420283a524406d2addfdcc28b437db9 /README.md | |
| parent | b75ba216d1020212662f870306ebbeaf16e260fa (diff) | |
| download | vaultwarden-eb61425da5bd1be8e386cc67da15655c9462fbd1.tar.gz vaultwarden-eb61425da5bd1be8e386cc67da15655c9462fbd1.zip | |
Update README.md
Added infos about enabling https when softwares getting certs are using symlinks
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 14 |
1 files changed, 14 insertions, 0 deletions
@@ -176,6 +176,20 @@ docker run -d --name bitwarden \ ``` Note that you need to mount ssl files and you need to forward appropriate port. +Softwares used for getting certs are often using symlinks. If that is the case, both locations need to be accessible to the docker container. +Example: certbot will create a folder that contains the needed cert.pem and privacy.pem files in /etc/letsencrypt/live/mydomain/ + +These files are symlinked to ../../archive/mydomain/mykey.pem + +So to use from bitwarden container: + +```sudo docker run -d --name bitwarden \ + -e ROCKET_TLS='{certs="/ssl/live/mydomain/cert.pem",key="/ssl/live/mydomain/privkey.pem"}' \ + -v /etc/letsencrypt/:/ssl/ \ + -v /bw-data/:/data/ \ + -p 443:80 \ + mprasil/bitwarden:latest +``` ### Enabling WebSocket notifications *Important: This does not apply to the mobile clients, which use push notifications.* |