runOnStartup watch option

This commit is contained in:
CrazyMax
2023-06-12 00:04:59 +02:00
parent 352989524a
commit 780f3fb81f
6 changed files with 27 additions and 68 deletions

View File

@@ -34,6 +34,7 @@ You can override this using the [`--config` flag or `CONFIG` env var with `serve
schedule: "0 */6 * * *"
jitter: 30s
firstCheckNotif: false
runOnStartup: true
notif:
amqp:
@@ -129,6 +130,7 @@ All configuration from file can be transposed into environment variables. As an
schedule: "0 */6 * * *"
jitter: 30s
firstCheckNotif: false
runOnStartup: true
notif:
gotify:
@@ -183,6 +185,7 @@ Can be transposed to:
DIUN_WATCH_SCHEDULE=0 */6 * * *
DIUN_WATCH_JITTER=30s
DIUN_WATCH_FIRSTCHECKNOTIF=false
DIUN_WATCH_RUNONSTARTUP=true
DIUN_NOTIF_GOTIFY_ENDPOINT=http://gotify.foo.com
DIUN_NOTIF_GOTIFY_TOKEN=Token123456

View File

@@ -8,6 +8,7 @@ watch:
schedule: "0 */6 * * *"
jitter: 30s
firstCheckNotif: false
runOnStartup: true
compareDigest: true
healthchecks:
baseURL: https://hc-ping.com/
@@ -76,6 +77,19 @@ Send notification at the very first analysis of an image. (default `false`)
!!! abstract "Environment variables"
* `DIUN_WATCH_FIRSTCHECKNOTIF`
### `runOnStartup`
Check for updates on startup. (default `true`)
!!! example "Config file"
```yaml
watch:
runOnStartup: true
```
!!! abstract "Environment variables"
* `DIUN_WATCH_RUNONSTARTUP`
### `compareDigest`
Compare the digest of an image with the registry before downloading the image manifest. It is strongly