From de49af4806abf02c5151ba87cbeca90d4e8824be Mon Sep 17 00:00:00 2001 From: "Simon L." Date: Sat, 25 Jan 2025 02:29:23 +0100 Subject: [PATCH] add empty line Signed-off-by: Simon L. --- reverse-proxy.md | 1 + 1 file changed, 1 insertion(+) diff --git a/reverse-proxy.md b/reverse-proxy.md index 89aca458..52f917a2 100644 --- a/reverse-proxy.md +++ b/reverse-proxy.md @@ -2,6 +2,7 @@ > [!NOTE] > Please note that AIO comes secured with TLS out-of-the-box. So you don't need to necessarily set up your own reverse proxy if you only want to run Nextcloud AIO which is much easier. See [the normal readme](https://github.com/nextcloud/all-in-one?tab=readme-ov-file#how-to-use-this) in that case. However if port 443 should already be used because you already run a web server or reverse proxy (like Apache, Nginx, Caddy, Cloudflare Tunnel and else), you need to follow this reverse proxy documentation to set up Nextcloud AIO. + > [!TIP] > If you don't have a domain yet, [Tailscale is recommended](https://github.com/nextcloud/all-in-one/discussions/5439). If you don't have a reverse proxy yet, [Caddy is recommended](https://github.com/nextcloud/all-in-one/discussions/575).