From 0274af2b8b806929444a1cb1c1988efe55c00a19 Mon Sep 17 00:00:00 2001 From: DoTheEvolution Date: Fri, 1 May 2020 01:51:39 +0200 Subject: [PATCH] update --- caddy_v2/readme.md | 21 ++++++++++++++++++--- 1 file changed, 18 insertions(+), 3 deletions(-) diff --git a/caddy_v2/readme.md b/caddy_v2/readme.md index defc725..d9310ed 100644 --- a/caddy_v2/readme.md +++ b/caddy_v2/readme.md @@ -258,10 +258,25 @@ b.blabla.org { But there are some cases that want something extra, as shown in following examples. -### Reverse proxy without names just for LAN +### Routing traffic to other machines on the LAN -If some containers should be accessed only from LAN with no interest in -domains and https and all that noise. +If not targeting a docker container but a dedicated machine on the network.
+Nothing really changes, if you can ping the machine from Caddy container +by its hostname or its IP, it will work. + +``` +blue.{$MY_DOMAIN} { + reverse_proxy server-blue:80 +} + +violet.{$MY_DOMAIN} { + reverse_proxy 192.168.1.100:80 +} +``` + +### Reverse proxy without domain and https + +You can always just use localhost, which will translates in to docker hosts IP address. ``` localhost:55414 {