Conversation
Uses apprise sidecar url, if configured, to send an "info" notification after each run of the update_services loop. Closes: #95
|
Sorry for the late response. Not sure if everyone would want this. Maybe we could make it optional via an env variable? |
|
@djmaze - i think this would be a great addition as a an env variable. Additionally, i think you should include at least an initial notification just to confirm that it is up and running and properly connected to the messaging endpoint...just like watchtower does right now. Watchtower sends a quick notification so why not have Shepherd do the same? |
|
@virtualex-itv Watchtower sends an initial notification? Upon start of the container? Or upon every update cycle? I guess the first one does not really have much value because you won't know if it is suddenly not working anymore. |
|
@djmaze - correct. Upon initial start up post-deployment and every time there's an image updated. |
|
Yeah, but then let's better put it in front of an additional env variable. Something like |
|
That would work too. Some type of option is better than no option at all. 🦾 |
3 participants
Uses apprise sidecar url, if configured, to send an "info" notification after each run of the update_services loop.
Closes: #95