Checks doc: mention dokku checks disable at the top, before we get into the custom checks explanation
This commit is contained in:
@@ -13,6 +13,12 @@ dokku config:set --global DOKKU_DEFAULT_CHECKS_WAIT=30
|
|||||||
dokku config:set <app> DOKKU_DEFAULT_CHECKS_WAIT=30
|
dokku config:set <app> DOKKU_DEFAULT_CHECKS_WAIT=30
|
||||||
```
|
```
|
||||||
|
|
||||||
|
You can also choose to skip checks completely on a per-application basis:
|
||||||
|
|
||||||
|
```shell
|
||||||
|
dokku checks:disable <app>
|
||||||
|
```
|
||||||
|
|
||||||
Dokku will wait `60` seconds before stopping the old container so that existing connections are given a chance to complete. You can modify this value globally or on a per-application basis:
|
Dokku will wait `60` seconds before stopping the old container so that existing connections are given a chance to complete. You can modify this value globally or on a per-application basis:
|
||||||
|
|
||||||
```shell
|
```shell
|
||||||
@@ -46,12 +52,6 @@ Dokku will retry the checks `5` times until the checks are successful. If all 5
|
|||||||
dokku config:set --global DOKKU_CHECKS_ATTEMPTS=2
|
dokku config:set --global DOKKU_CHECKS_ATTEMPTS=2
|
||||||
```
|
```
|
||||||
|
|
||||||
You can also choose to skip checks completely on a per-application basis:
|
|
||||||
|
|
||||||
```shell
|
|
||||||
dokku checks:disable <app>
|
|
||||||
```
|
|
||||||
|
|
||||||
## Checks Examples
|
## Checks Examples
|
||||||
|
|
||||||
The CHECKS file may contain empty lines, comments (lines starting with #),
|
The CHECKS file may contain empty lines, comments (lines starting with #),
|
||||||
|
|||||||
Reference in New Issue
Block a user