mirror of
https://github.com/dani-garcia/vaultwarden
synced 2024-11-16 23:11:59 +01:00
add link to Docker Compose example
parent
70fc985b62
commit
f1fffb5552
1 changed files with 2 additions and 0 deletions
|
@ -2,6 +2,8 @@ Suppose you want to run an instance of bitwarden_rs that can only be accessed fr
|
|||
|
||||
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 bitwarden_rs. See [Using Docker Compose](https://github.com/dani-garcia/bitwarden_rs/wiki/Using-Docker-Compose#caddy-with-dns-challenge) for an example specific to that.)
|
||||
|
||||
Two DNS providers are covered:
|
||||
|
||||
* [Duck DNS](https://www.duckdns.org/) -- This gives you a subdomain under `duckdns.org` (e.g., `my-bwrs.duckdns.org`). This option is simplest if you don't already own a domain.
|
||||
|
|
Loading…
Reference in a new issue