diff --git a/en_US/cloud/cloud-best.practice.md b/en_US/cloud/cloud-best.practice.md index a94b18c9..37e78095 100644 --- a/en_US/cloud/cloud-best.practice.md +++ b/en_US/cloud/cloud-best.practice.md @@ -42,10 +42,11 @@ max_connections = 1024 - a bash shell script for advanced customization. This file will be executed every time iRedMail cloud platform deploys / upgrades the Nginx component. - A sample usage: Nginx doesn't support override existing settings by - same parameter from another config file, so you can use `rm` command in - this file (`custom.sh`) to remove the config file generated by iRedMail - cloud platform. + For example, Nginx doesn't support override existing settings by + loading same parameter from another config file, in this case you should + run `rm` command in this file (`custom.sh`) to remove existing config + file generated by iRedMail cloud platform and store custom settings in + another file. - `/opt/iredmail/custom/nginx/conf-enabled/`: additional Nginx global settings used inside `http {}` block. - If you want to override a parameter which is already defined in diff --git a/html/cloud-best.practice.html b/html/cloud-best.practice.html index 40c478be..a497a8ca 100644 --- a/html/cloud-best.practice.html +++ b/html/cloud-best.practice.html @@ -78,10 +78,11 @@ max_connections = 1024
A sample usage: Nginx doesn't support override existing settings by
- same parameter from another config file, so you can use rm
command in
- this file (custom.sh
) to remove the config file generated by iRedMail
- cloud platform.
For example, Nginx doesn't support override existing settings by
+ loading same parameter from another config file, in this case you should
+ run rm
command in this file (custom.sh
) to remove existing config
+ file generated by iRedMail cloud platform and store custom settings in
+ another file.
/opt/iredmail/custom/nginx/conf-enabled/
: additional Nginx global settings used inside http {}
block.