github-repos/acme.sh
1
0
Fork 0
mirror of https://github.com/acmesh-official/acme.sh.git synced 2025-03-24 18:40:09 +08:00
Code Issues Packages Projects Releases Wiki Activity

Updated deployhooks (markdown)

Scruel Tao 2024-04-22 11:26:02 +08:00
parent 015764ffc9
commit ee779d7db9
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
deployhooks.md

@ -611,8 +611,6 @@ As pointed out [inside the deploy script file](https://github.com/acmesh-officia
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.
- Use your existing admin user by provide its credential (username, password, OTP):
1. Execute `export SYNO_USERNAME="adminUser"` where `adminUser` is any user with sufficient administrative rights, e. g. `admin`.
2. Execute `export SYNO_PASSWORD="adminPassword"` where `adminPassword` is the chosen user's password.
@ -674,6 +672,8 @@ acme.sh --deploy --insecure --deploy-hook synology_dsm -d example.com
Though, enabling HTTP/2 still might give you a `curl 16 error` warning, although the script succeeded anyways.
Additionally, if you choose to use temp admin user method, and to prevent confusion, the value of `SYNO_HOSTNAME` must targets to current local machine (e.g., `localhost` or `127.0.0.1`), however if your custom SYNO_HOSTNAME does indeed target to current local machine, you can execute `export SYNO_LOCAL_HOSTNAME=1` to explicitly declare it before deploying.
When issuing a certificate (e.g., Let's Encrypt) for the first time instead of renewing it, `export SYNO_CREATE=1` must be executed once.
Any subsequent run won't need that variable, hence it's not saved within your configuration file at all.