restic-automatic-backup-scheduler VS podman-nginx-socket-activation

I really like restic, and am personally happy to use it via the command line. It's very fast and efficient! However, I do wish there was better tooling / wrappers around it. For example, Pika Backup is a popular UI for Borg of which no equivalent exists for Restic. I'd love to be able to set something simple up on my partner's Macbook.

For my own purposes, I've been using a script I found on Github[0] for a while, but it only really supports Backblaze B2 AFAIK.[1]

I've been meaning to try autorestic[2] and resticprofile[3] as they are potentially more flexible than the script I'm currently using, and prestic[4] looks intriguing for my partner's use, but seems to have very few users. And the fact that there are so many competing tools makes it difficult to land on one.

[0] https://github.com/erikw/restic-automatic-backup-scheduler

[1] https://github.com/erikw/restic-automatic-backup-scheduler/i...

[2] https://github.com/cupcakearmy/autorestic

[3] https://github.com/creativeprojects/resticprofile

[4] https://github.com/ducalex/prestic

https://github.com/eriksjolund/podman-nginx-socket-activatio...

I wrote an nginx socket activation example https://github.com/eriksjolund/podman-nginx-socket-activation (The example does not show nginx working as HTTP reverse proxy but I think tried that out before and it worked)

(I wrote a demo: https://github.com/eriksjolund/podman-nginx-socket-activation)

The difference is that with Podman its possible to create a systemd socket unit for the service (for example nginx.socket).

The problem when running rootless Podman with socket activation and docker.io/library/nginx is caused by the closing of file descriptor 3 in /entrypoint.sh.