diff options
| author | Michał M. Sapka <michal@sapka.me> | 2023-03-08 14:53:32 +0100 |
|---|---|---|
| committer | Michał M. Sapka <michal@sapka.me> | 2023-03-08 14:53:32 +0100 |
| commit | 06b3bb4cceb6f4cb41c18ec6b3083e1a96d600b3 (patch) | |
| tree | 0c2abdd45fec2d949206729bf48fd860ce5fddb5 | |
| parent | b2cc8371b83c4ae7023f52a0c038aee2568cdfe7 (diff) | |
fix: typo
| -rw-r--r-- | content/2023/always-have-the-entire-network-in-mind.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/content/2023/always-have-the-entire-network-in-mind.md b/content/2023/always-have-the-entire-network-in-mind.md index 2a731ef..a98c6ee 100644 --- 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. |