From 2c4f3f481f94bdcb9ce2f98c4ca420fe21e5badb Mon Sep 17 00:00:00 2001 From: sn0w Date: Sun, 25 Aug 2019 23:43:43 +0200 Subject: [PATCH] update readme --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 26b2c0f..e3f7c35 100644 --- a/README.md +++ b/README.md @@ -109,7 +109,7 @@ This will work automagically when the proxy also lives inside of docker. Something that cofe.rocks uses is simple port-forwarding of the `server` container to the host's `127.0.0.1`. From there on, the natively installed nginx server acts as a proxy to the open internet. -You can take a look at [this file](https://glitch.sh/hosted/pleroma/src/commit/4e88d93276f0bb2ef62d7f18477b156318924325/docker-compose.m4#L93) if that setup sounds interesting. +You can take a look at [this file](https://glitch.sh/hosted/pleroma/src/commit/4e88d93276f0bb2ef62d7f18477b156318924325/docker-compose.m4#L93) and [cofe's proxy config](https://glitch.sh/hosted/pleroma/src/commit/4e88d93276f0bb2ef62d7f18477b156318924325/proxy.xconf) if that setup sounds interesting. If you need help with this, or if you think that this needs more documentation, please let me know.