From 0f404b439ec264885434e677fae0d3880d406495 Mon Sep 17 00:00:00 2001
From: y2keui <y2keui@nate.com>
Date: Sat, 6 Jun 2026 15:29:10 +0900
Subject: [PATCH] =?UTF-8?q?NAS=20=ED=94=84=EB=A1=9D=EC=8B=9C=20=EB=B0=B0?=
 =?UTF-8?q?=ED=8F=AC=20=EA=B8=B0=EB=A1=9D=20=EC=B6=94=EA=B0=80?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/SYNOLOGY.md | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/docs/SYNOLOGY.md b/docs/SYNOLOGY.md
index 3ab6306..7db281a 100644
--- a/docs/SYNOLOGY.md
+++ b/docs/SYNOLOGY.md
@@ -18,6 +18,7 @@ The first NAS deployment was verified on 2026-06-06 with:
 Project name: cargoradar
 Project path: /volume1/docker/cargoradar/current
 LAN URL:      http://192.168.200.129:18081
+Public URL:   https://cargoradar.comtropy.synology.me
 ```
 
 The Container Manager build should end with `Exit Code: 0`, and the server
@@ -27,6 +28,17 @@ Keep the real `ADMIN_TOKEN` in the NAS `.env` file, not in committed docs.
 When creating `.env` remotely, make sure each setting is on its own real line;
 literal `\n` text inside the file will break Docker Compose port parsing.
 
+The current reverse proxy rule is:
+
+```text
+Source: HTTPS cargoradar.comtropy.synology.me:443
+Target: HTTP  localhost:18081
+```
+
+If browsers show an HTTPS trust warning, assign or issue a certificate that
+covers `cargoradar.comtropy.synology.me`. The reverse proxy can still be smoke
+tested with `curl -k` while the certificate is being prepared.
+
 ## Environment
 
 ```text