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-02-28 16:42:28 +08:00
parent 4288288b6b
commit d9a1be9ed1
1 changed files with 3 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
deployhooks.md

@ -598,12 +598,11 @@ acme.sh --deploy -d example.com --deploy-hook panos --insecure
As pointed out [inside the deploy script file](https://github.com/acmesh-official/acme.sh/blob/ff090d2f74f994da4bca89b942b08bb714b25a46/deploy/synology_dsm.sh#L11-L38) itself, only 3 simple steps are required for deploy:
1. Set the required environment variables which used for authentication while deploying:
- (Recommend) Use an automatically created temp admin user by executing `export SYNO_USE_TEMP_ADMIN=1`.
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, it depends on Synology built-in utils to achieve such convenience, as it is designed to only support locally deployment, it can't be used to deploy in docker or deoply remotely. To prevent confusion, the value of `SYNO_HOSTNAME` must targets current local machine (can be `localhost` or `127.0.0.1`), however if your custom `SYNO_HOSTNAME` does indeed target to the current local machine, you should also execute `export SYNO_LOCAL_HOSTNAME=1` before deploying.
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".
After deployed done, the temp admin user should be automatically deleted after execution, if the script unexpectedly stopped while running (e.g., aborted by pressing "Ctrl+C"), it may remain if it has already been created, in this case, you can safely delete it via Control panel.
If you want to back to deploy with existing admin user, you need to execute `export CLEAR_SYNO_USE_TEMP_ADMIN=1`.
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`.