pixxon

Instrumenting the Go application is indeed fairly easy, since Prometheus itself provides the tools, but the issue here comes from the application not running continuously. This can be connected to...

I also considered this approach, but one major obstacle would be to figure out how to mount the volumes nicely for backup. I would not want every single volume to...

Maybe a wild take, but instead of adding the labels to __services__, one could add them to the __volumes__ themselves? Docker allows objects to be labeled, including volumes. Both the...

I have tried to make a quick mock example of what I was trying to explain above. This would certainly change the whole approach of the backup software. The need...

> how (and if even) such a configuration approach could be compatible with the existing one, or if this would require a hard cut? It would certainly be possible to...

> What happens if labels change, who's notfiying the backup container that it needs to create a new cron? What about bind mounts? The backup would need to poll the...

> this is not something I can implement easily in my free time (the way this project is currently run). Since this is something that I would like to use,...

I understand the concerns, I was not thinking of a single large PR either. The 1,2,3 order seems to be easier, especially since 1 is already in the form of...

I am not a fan of introducing persistence to a tool that should back that up. ( It would need to create a backup of its own? ) Regarding REST...

> how does this work in case I deploy multiple stacks that each run a offen/docker-volume-backup container (which I've seen people do from what is being posted in issues and...