Inspector 0.9.0: edit every container option and the Uptime Kuma / Portainer integrations in the dashboard
This commit is contained in:
1 parent
7013a13cba
commit
bd78835f4a
9 files changed
+681
-31
No files matched your search
@@ -69,18 +69,20 @@ download it and open it in a browser to read it here).
|
||||
|
||||
## Advanced options
|
||||
|
||||
Most people never need these. They live in `config.yml` (in your
|
||||
`INSPECTOR_DATA/config` folder) rather than the dashboard; see
|
||||
[`config.example.yml`](./config.example.yml) for every option with comments.
|
||||
Most people never need these. They are all on each container's page in the
|
||||
dashboard (and in `config.yml`, see
|
||||
[`config.example.yml`](./config.example.yml) for every option with comments).
|
||||
|
||||
- **HTTP checks**: mark a container `UNREACHABLE` when a URL stops answering,
|
||||
even if Docker says it's healthy (useful for apps behind a VPN container).
|
||||
- **Uptime Kuma**: use a Kuma status page as an extra reachability signal.
|
||||
**Test connection** lists the monitors Inspector can see.
|
||||
- **Dependencies** (`depends_on`): don't restart an app while the container it
|
||||
relies on (e.g. a VPN) is down.
|
||||
- **Portainer stack redeploy**: for containers that share a VPN container's
|
||||
network, recover by redeploying the whole stack instead of restarting one
|
||||
container.
|
||||
container. Set up the Portainer connection under **Settings → Portainer**;
|
||||
**Test connection** lists your stacks.
|
||||
|
||||
## Security
|
||||
|
||||
|
||||
Reference in new issue
Block a user