commit 06b3bb4cceb6f4cb41c18ec6b3083e1a96d600b3 parent b2cc8371b83c4ae7023f52a0c038aee2568cdfe7 Author: MichaĆ M. Sapka <michal@sapka.me> Date: Wed, 8 Mar 2023 14:53:32 +0100 fix: typo Diffstat:
M | content/2023/always-have-the-entire-network-in-mind.md | | | 2 | +- |
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/2023/always-have-the-entire-network-in-mind.md b/content/2023/always-have-the-entire-network-in-mind.md @@ -20,6 +20,6 @@ Guess what the problem was. Of course, as always, it was the sysadmin. -Synology is plug-and-play enough to use UPnP. My poor docker-locked clients did now. I needed to create a forwarding rule on my router which would point the port to the Synology and configure Docker to forward the port to the Docker container. +Synology is plug-and-play enough to use UPnP. My poor docker-locked clients did not. I needed to create a forwarding rule on my router which would point the port to the Synology and configure Docker to forward the port to the Docker container. I am not a smart admin.