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 ff8eeff995d9ddd7f64cb610453f43470c3eefef
parent e7dd239d20d35d227f1c365844571cdf53486e6c
Author: Daniel GarcĂ­a <dani-garcia@users.noreply.github.com>
Date:   Sun, 16 Sep 2018 15:44:05 +0200

Merge pull request #184 from mprasil/code_block_fix

Fixed code block, added some formatting
Diffstat:
MREADME.md | 8+++++---
1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md @@ -177,13 +177,15 @@ 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 +Example: [certbot](https://certbot.eff.org/) 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 \ +```sh +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/ \