Updated Synology NAS Guide (markdown)
parent
4ceaabf96f
commit
b6d1e91a4a
|
@ -72,8 +72,6 @@ In this way, you won't need to provide any admin credentials, the deploy sciprt
|
|||
|
||||
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".
|
||||
|
||||
Additionally, 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.
|
||||
|
||||
#### Deploy with existing admin user
|
||||
If you prefer to deploy with existing admin user or if the above way is not available (e.g., installed in docker, want to deploy remotely, etc.), you need to provide your own credentials:
|
||||
```sh
|
||||
|
@ -100,6 +98,9 @@ export SYNO_PORT="5001"
|
|||
$ ./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.
|
||||
|
||||
|
||||
### Deploying additional certificates
|
||||
|
||||
By specifying a different `SYNO_CERTIFICATE` (and set `SYNO_CREATE=1` for creating), we can deploy multiple certificates to the DSM.
|
||||
|
|
Loading…
Reference in New Issue