Raj Dave
Raj Dave
I support @altendorfme's suggestion: Just like volumes, databases should be a separate section like volumes. It'll keep the codebase less cluttered as non-volumes wouldn't need to be grouped with volumes....
From what I understand, creating a pre/post backup hook that executes commands/interacts with the host OS isn't going to be easy since this container is dockerized. (look at #49) Either...
> It can be accomplished by including the docker cli and mounting the docker socket to dump other containers. I do agree though that this adds both complexity and risk...
Did you modify the TZ= after creating the backup schedules by any chance?