asif/MailcowBackup
1
0
Fork 0
Code Issues Releases 10 Wiki Activity

readme: updated 503 functionality section

Browse Source
This commit is contained in:
Asif Bacchus 2018-10-21 17:24:06 -06:00
parent be015042c7
commit 119b9a8b0d
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
README.md
View File

@ -326,8 +326,8 @@ ### Conditional forwarding by your webserver
The script copying the file to the webroot is the easy part. Your webserver has The script copying the file to the webroot is the easy part. Your webserver has
to look for the presence of that file and generate a 503 error in order for the to look for the presence of that file and generate a 503 error in order for the
magic to happen. To do that, you have to include an instruction to that effect magic to happen. To do that, you have to include an instruction to that effect
in your default server definition and/or your Mailcow virtual server in your default server definition and/or your Mailcow virtual server definition
definition file depending on your setup. file depending on your setup.
#### NGINX #### NGINX
@ -350,11 +350,11 @@ #### NGINX
``` ```
This tells NGINX that if it finds the file *'503.html'* at the path This tells NGINX that if it finds the file *'503.html'* at the path
*'/usr/share/nginx/html'* (webroot) then return an error code 503. Next, *'/usr/share/nginx/html'* (webroot on reverse proxy) then return an error code
rewrite any url to *'domain.tld/503.html'* and thus, display the custom 503 503. Next, rewrite any url to *'domain.tld/503.html'* and thus, display the
error page. On the other hand, if it can't find 503.html at the path specified custom 503 error page. On the other hand, if it can't find 503.html at the path
(i.e. the script has deleted it because the backup is completed), then go about specified (i.e. the script has deleted it because the backup is completed), then
business as usual. go about business as usual.
#### Apache #### Apache