Added helpful note about cert and key paths using Docker.

brian bloom 2020-09-13 19:08:51 -04:00
parent e92a571267
commit 64c30b3a77

@ -19,6 +19,6 @@ certPath=/[username]/.acme.sh/[hostname]/fullchain.cer
keyPath=/[username]/.acme.sh/[hostname]/example.com.key keyPath=/[username]/.acme.sh/[hostname]/example.com.key
``` ```
Above is only example of how this is setup on my environment when I generated the certificate using Let's encrypt acme utility. Your paths may be completely different. Above is only example of how this is setup on my environment when I generated the certificate using Let's encrypt acme utility. Your paths may be completely different. (Note that if you are using a Docker installation, these paths should be in a volume or other path understood by the docker container.)
After you set this up, you may restart trilium and now visit the hostname with "https". After you set this up, you may restart trilium and now visit the hostname with "https".