From d171fb86aff9e5e03b3cc33df2e5a55db90faa78 Mon Sep 17 00:00:00 2001 From: Artur Klauser Date: Wed, 19 Feb 2025 17:13:09 -0800 Subject: [PATCH] Fixing typo --- 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 0ee7b69..479c611 100644 --- a/Synology-NAS-Guide.md +++ b/Synology-NAS-Guide.md @@ -70,7 +70,7 @@ export SYNO_USE_TEMP_ADMIN=1 ./acme.sh --deploy --home . -d "$CERT_DOMAIN" --deploy-hook synology_dsm ``` -In this way, you won't need to provide any admin credentials, the deploy sciprt itself will utilize Synology built-in utils to complete authentication, so it designed to only support locally deployment, and can't be used to deploy in docker or deploy remotely. +In this way, you won't need to provide any admin credentials, the deploy script itself will utilize Synology built-in utils to complete authentication, so it designed to only support locally deployment, and can't be used to deploy in docker or deploy remotely. Script will load previous saved conf for subsequent deployments, so if you want to back to deploy with existing admin user, you need to execute `export CLEAR_SYNO_USE_TEMP_ADMIN=1` first. After deploy script exits, the temp admin user should either not have been created or has already been deleted, however it may still remain if script exits unexpectedly (e.g., aborted by pressing "Ctrl+C"), in this case, you can safely delete it via "Control Panel".