Fred

I've installed version 0.14.0, converted my repositories, and I haven't had any issue so far. The only issue I can see for now, is the use of the now deprecated...

Hi, If you look at the restic inline help, the `host` flag is not a global flag nor it is a specific flag on the `init` command: ``` % restic...

> * Would it still be scalable with docker compose? > (not a problem for me now) It looks like it is supported in docker compose (I haven't tested it)...

> I probably described it not good enough, I meant you cannot scale=2 (or more) because you would have duplicate hostnames/dns names. But I also couldn't find any evidence or...

I was preparing version 0.18.0 but I can squeeze that in 👍🏻

Yeah it looks good to me, I do like how it simplifies the profiles actually 😄 Thanks for that, it's really cool 👍🏻

I see, this is getting a bit complicated to follow. There's probably no need for so many run targets TBH. There isn't a run-after-fail for any command just now and...

> check, forget, init & prune also inherit the run hooks but they are only run when these commands are executed directly (not for indirect invocation via backup). Likely it...

That's also a good idea. Or even maybe create a `scripts` section like: ```yaml profiles: new: backup: source: / scripts: full_backup: - check - backup - copy - forget ```...

Yes, I do like the concept of aliases. Simple to understand, and reusable across profiles. Using internal aliases to mimic the existing configuration would work very well to keep compatibility...