From 97dd8e2f9b872dbcbfd5129aa02053aef3b2d6e2 Mon Sep 17 00:00:00 2001
From: jaku2019 <55255300+jaku2019@users.noreply.github.com>
Date: Wed, 5 Jun 2024 01:16:51 +0200
Subject: [PATCH] correct $./acme.sh to ./acme.sh in copy command section

---
 Synology-NAS-Guide.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Synology-NAS-Guide.md b/Synology-NAS-Guide.md
index 3e5b1ab..7a3b21f 100644
--- a/Synology-NAS-Guide.md
+++ b/Synology-NAS-Guide.md
@@ -95,7 +95,7 @@ When we want to use HTTPS to deploy the new certificate and connect to "localhos
 # export SYNO_HOSTNAME="localhost" # Specify if not using on localhost
 export SYNO_SCHEME="https"
 export SYNO_PORT="5001"
-$ ./acme.sh --deploy --insecure --home . -d "$CERT_DOMAIN" --deploy-hook synology_dsm
+./acme.sh --deploy --insecure --home . -d "$CERT_DOMAIN" --deploy-hook synology_dsm
 ```
 
 Additionally, if you are using temp admin method to deploy, to prevent confusion, the value of `SYNO_HOSTNAME` must targets to current local machine (can be `localhost` or `127.0.0.1`), however if your custom SYNO_HOSTNAME does indeed target to current local machine, you should execute `export SYNO_LOCAL_HOSTNAME=1` before deploying.