modem7

> I was able to retool my configuration and get this to work: > > `S6_KEEP_ENV=1` as an environment value > I moved my borg password to a secret and...

> No worries. i feel the issue was user error. I appreciate your guys work. It's unfortunately a bit of both. We introduced a breaking change with S6 affecting a...

@grantbevis yes, the only reason supercronic was in was to address the sigterm issue which it didn't really do anyway. Since moving to s6, it's less maintenence and more reliable...

> > We need to update and go through the readme and update since we're missing a few things. > > A migration guide would be great because it seems...

> It seems it is not that easy to move an existing crontab to s6. I changed the number of fields from 6 to 5 but yet I get a...

OK, I think I've found the issue. I'm going to raise a PR, and we'll need to change your crontab as well to work a bit better.

I've raised https://github.com/borgmatic-collective/docker-borgmatic/pull/322. @grantbevis could you review and authorise? Single line change. To make this work better, change the crontab to be: ``` # Backup hourly from 8:00 to 22:00...

@MarkJonas - Does this work for you?

Heya, Yes, the readme needs an overhaul as we've have a lot of changes in a short period of time. But effectively, it merely transposes cron from a file to...

> Hey guys, quite busy recently and haven't been able to spend much time going over this. I have just tested today with the latest pi.hole version and everything seems...