* Add monitor-only label
* Add tests for monitor-only
* Treat missing monitor-only label as if the option was set to false
* Add docs for container-based monitor-only
* Add function doc
* Fix monitor-only logic
* implement rolling restart functionality
bouncing each image individually can ensure that a group of docker
containers launched with docker-compose can stay 100% up during deploy.
* move rolling restart into a function
* honor params.Cleanup
Co-authored-by: Simon Aronsson <simme@arcticbit.se>
* Adds scopeUID config to enable multiple instances of Watchtower
* Adds tests for multiple instance support with scopeuid
* Adds docs on scope monitoring and multiple instance support
* Adds multiple instances docs to mkdocs config file
* Changes multiple instances check and refactors naming for scope feature
* Applies linter suggestions
* Fixes documentation on Watchtower monitoring scope
* Revert "Image of running container no longer needed locally (#571)"
This reverts commit 6da66fb312.
* Update client.go
* fix: skip updating when no image info can be retrieved
This will allow watchtower to continue even though the image info for a
container cannot be retrieved. If this happens one warning will be emitted
and the container will be skipped, unless NoRestart or OnlyMonitor is supplied
* A warning was added if `WATCHTOWER_NO_PULL` and` WATCHTOWER_MONITOR_ONLY` are used simultaneously
* Update root.go
Co-authored-by: Simon Aronsson <simme@arcticbit.se>
The life-cycle messages should not have the same level as the update messages.
Why?
I receive a (mail-) notification for every run even if no image is changed:
```
2020-07-31 06:44:33 (info): Executing pre-check command.
```
But I only want to receive a notification if something changed:
```
2020-07-20 06:44:44 (info): Found new traefik:v2.2 image (sha256:7c992081f52423e325bd12debf0edcb4f7cfa398683c26f99c00112ec14e1ab9)
```
* Added string functions for lowercase, uppercase and capitalize to shoutrrr templates
* Update pkg/notifications/shoutrrr.go
Co-authored-by: nils måsén <nils@piksel.se>
* Update pkg/notifications/shoutrrr.go
Co-authored-by: nils måsén <nils@piksel.se>
* Update pkg/notifications/shoutrrr.go
Co-authored-by: nils måsén <nils@piksel.se>
* Update pkg/notifications/shoutrrr_test.go
Co-authored-by: nils måsén <nils@piksel.se>
* escape quotation marks in test
Co-authored-by: nils måsén <nils@piksel.se>
* Allows options containing sensitive stuff (passwords, tokens) to be passed as a file instead
* Fixed linter error, added tests, removed notification-url (due to being an array)
The notification shows an example of how to get it working for gmail smtp servers, but it's missing the port parameter required to get the SMTP connection working.
Without this setting, you get a "connection refused" connecting to port 25.
Given the popularity of gmail, it would be nice to have this example more accurate.
David H