From 64c30b3a77b2f5409fa87df388fd6f7468dcc72e Mon Sep 17 00:00:00 2001 From: brian bloom Date: Sun, 13 Sep 2020 19:08:51 -0400 Subject: [PATCH] Added helpful note about cert and key paths using Docker. --- TLS configuration.md => TLS-configuration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename TLS configuration.md => TLS-configuration.md (87%) diff --git a/TLS configuration.md b/TLS-configuration.md similarity index 87% rename from TLS configuration.md rename to TLS-configuration.md index 6c99c82..b4c608b 100644 --- a/TLS configuration.md +++ b/TLS-configuration.md @@ -19,6 +19,6 @@ certPath=/[username]/.acme.sh/[hostname]/fullchain.cer 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". \ No newline at end of file