From cccbcede85fd1722291ec51c0c33a6a2e0cda8af Mon Sep 17 00:00:00 2001 From: Pascal Vizeli Date: Wed, 16 Sep 2020 11:21:56 +0200 Subject: [PATCH] add watchdog --- docs/add-ons/configuration.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/add-ons/configuration.md b/docs/add-ons/configuration.md index fe9e3fb27c9..023df94a754 100644 --- a/docs/add-ons/configuration.md +++ b/docs/add-ons/configuration.md @@ -164,6 +164,7 @@ The configuration for an add-on is stored in `config.json`. | advanced | bool | no | Default `false`. Make addon visible in simple mode. | stage | string | no | Default `stable`. Flag add-on with follow attribute: `stable`, `experimental` or `deprecated` | init | bool | no | Default `true`. Disable the Docker default system init. Use this if the image has its own init system. +| watchdog | string | no | An URL for monitor an application this add-on. Like `http://[HOST]:[PORT:2839]/dashboard`, the port needs the internal port, which will be replaced with the effective port. It is also possible to bind the protocol part to a configuration options with: `[PROTO:option_name]://[HOST]:[PORT:2839]/dashboard` and it's looked up if it is `true` and it's going to `https`. For simple TCP port monitoring you can use `tcp://[HOST]:[PORT:80]`. It work for add-ons on host or internal network. ### Options / Schema