|
|
|
@ -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.*
|
|
|
|
|
|
|
|
|
|