From ce7d75b41985e7bc548b34bdd112c01c3adf2a25 Mon Sep 17 00:00:00 2001 From: Jeremy Lin Date: Tue, 14 Dec 2021 14:35:54 -0800 Subject: [PATCH] Emphasize Docker Compose docs --- ...g-a-private-vaultwarden-instance-with-Let's-Encrypt-certs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Running-a-private-vaultwarden-instance-with-Let's-Encrypt-certs.md b/Running-a-private-vaultwarden-instance-with-Let's-Encrypt-certs.md index 70f2360..55e9906 100644 --- a/Running-a-private-vaultwarden-instance-with-Let's-Encrypt-certs.md +++ b/Running-a-private-vaultwarden-instance-with-Let's-Encrypt-certs.md @@ -2,7 +2,7 @@ Suppose you want to run an instance of vaultwarden that can only be accessed fro This article demonstrates how to create such a setup using the [Caddy](https://caddyserver.com/) web server, which has built-in ACME support for various DNS providers. We'll configure Caddy to obtain Let's Encrypt certs via the ACME [DNS challenge](https://letsencrypt.org/docs/challenge-types/#dns-01-challenge) -- using the more common HTTP challenge would be problematic here, since it would rely on Let's Encrypt servers being able to reach your internal web server. -(Note that this article covers the DNS challenge setup in more generic terms, but many users will probably find it easiest to use Docker Compose to integrate Caddy and vaultwarden. See [Using Docker Compose](https://github.com/dani-garcia/vaultwarden/wiki/Using-Docker-Compose#caddy-with-dns-challenge) for an example specific to that.) +:warning: This article covers the DNS challenge setup in more generic terms, but many users will probably find it easiest to use Docker Compose to integrate Caddy and Vaultwarden. See [Using Docker Compose](https://github.com/dani-garcia/vaultwarden/wiki/Using-Docker-Compose#caddy-with-dns-challenge) for an example specific to that. Two DNS providers are covered: