DEPLOY_ENV_LIST: Used to control the list of environments that need to be installed
DEPLOY_ENV_EXCLUDE: Used to control the list of environments that don't need to be installed
DEPLOY_DEPS_LIST: Used to control the list of deps that need to be installed
DEPLOY_DEPS_EXCLUDE: Used to control the list of deps that don't need to be installed
DEPLOY_SERVER_LIST: Used to control the list of service that need to be installed
DEPLOY_SERVER_EXCLUDE: Used to control the list of service that don't need to be installed
example 1: (The following command will install all envs,deps and serivce except hotfix service):
DEPLOY_SERVER_EXCLUDE=sysom_hotfix,sysom_hotfix_builder ./deploy.sh
example 2: (The following command will install all envs,deps, then only install sysom_api service):
DEPLOY_SERVER_LIST=sysom_api ./deploy.sh
1. "deploy.sh": Defines each component deployment phase operation (requires no dependency on other microservices, no dependency on any runtime environment, the main task is file deployment, dependency installation);
2. "init.sh": Contains initialization operations before the program is run for the first time, and can rely on other runtimes, for example, microservices can assume that the database has been started and can perform operations such as database migration;
1. Support for managing nodes with non-root users, require target user can run all command without password, you can edit "/etc/sudoers", add the following line. (replace <username> to target username)
<username> ALL=(ALL) NOPASSWD: ALL
2. When channel_job sends a command, it supports specifying that the command does not require root privileges, and when the username is not root, sudo bash -c "" will not be used to wrapper command
SunnyQjm