Browse Source

Merge pull request #184 from mprasil/code_block_fix

Fixed code block, added some formatting
pull/189/head
Daniel García 6 years ago
committed by GitHub
parent
commit
ff8eeff995
No known key found for this signature in database GPG Key ID: 4AEE18F83AFDEB23
  1. 8
      README.md

8
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. 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. 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: 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"}' \ -e ROCKET_TLS='{certs="/ssl/live/mydomain/cert.pem",key="/ssl/live/mydomain/privkey.pem"}' \
-v /etc/letsencrypt/:/ssl/ \ -v /etc/letsencrypt/:/ssl/ \
-v /bw-data/:/data/ \ -v /bw-data/:/data/ \

Loading…
Cancel
Save