From 39920fd1e61ff2754446a2e681c2e6d31df0c36f Mon Sep 17 00:00:00 2001 From: Davide Date: Sat, 28 Sep 2024 23:30:50 +0200 Subject: [PATCH] Modified README.md to include Memos example --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index d959c3b..f21bba7 100644 --- a/README.md +++ b/README.md @@ -12,7 +12,7 @@ Kubernetes has simply too much overhead for a small home lab like mine. I'm usin The only thing that would make me change idea would be a need for autoscaling, but I'm still far from that situation. ### How do I use this? -The `caddy-docker-proxy` is the first container that should be started, after running `$ docker network create caddy` to ensure the external network exists on the system. The `Caddyfile` included and mounted in `/etc/caddy/caddyfile` is used in this case to give access to the air-gapped comtainers running on different machines on the same network. +The `caddy-docker-proxy` is the first container that should be started, after running `$ docker network create caddy` to ensure the external network exists on the system. The `Caddyfile` included and mounted in `/etc/caddy/Caddyfile` is used in this case to give access to the air-gapped comtainers running on different machines on the same network. An example is found in the [Caddyfile](https://gitea.oddone.dev/Doddophonique/compose-personal-stack/src/branch/caddy-revamp/caddy-docker-proxy/Caddyfile), where the [Memos](https://gitea.oddone.dev/Doddophonique/compose-personal-stack/src/branch/caddy-revamp/memos/docker-compose.yml) container is exposed. As you can see, this is a borderline situation where some people may prefer having service discovery with either Swarm or Kubernetes, but in my experience this is still not enough to call for that. ### Conclusion (for now):