docs: use github admonitions
These still need to be properly parsed.
This commit is contained in:
@@ -1,5 +1,6 @@
|
||||
# Zero Downtime Deploy Checks
|
||||
|
||||
> [!IMPORTANT]
|
||||
> New as of 0.5.0
|
||||
|
||||
```
|
||||
@@ -83,6 +84,7 @@ dokku checks:disable node-js-app worker
|
||||
|
||||
### Displaying checks reports for an app
|
||||
|
||||
> [!IMPORTANT]
|
||||
> New as of 0.8.1
|
||||
|
||||
You can get a report about the app's checks status using the `checks:report` command:
|
||||
@@ -135,6 +137,7 @@ dokku checks:report node-js-app --checks-disabled-list
|
||||
|
||||
## Customizing checks
|
||||
|
||||
> [!IMPORTANT]
|
||||
> New as of 0.31.0
|
||||
|
||||
If your application needs a longer period to boot up - perhaps to load data into memory, or because of slow boot time - you may also use Dokku's `checks` functionality to more precisely check whether an application can serve traffic or not.
|
||||
@@ -171,7 +174,8 @@ A healthcheck entry takes the following properties:
|
||||
- `uptime`: (default: `""` - none): Amount of time the container must be alive before the container is considered healthy. Any restarts will cause this to check to fail, and this check does not respect retries.
|
||||
- `wait`: (default: `5` seconds): Number of seconds to wait between healthcheck attempts.
|
||||
|
||||
> Warning: Healthchecks are implemented by specific scheduler plugins, and not all plugins support all options. Please consult the scheduler documentation for further details on what is supported.
|
||||
> [!WARNING]
|
||||
> Healthchecks are implemented by specific scheduler plugins, and not all plugins support all options. Please consult the scheduler documentation for further details on what is supported.
|
||||
|
||||
See the [docker-container-healthchecker](https://github.com/dokku/docker-container-healthchecker) documentation for more details on how healthchecks are interpreted.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user