zrepl VS webhook

Lastly there is zrepl. This is an automatic snapshot creation, pruning and replication daemon. It lets you automate the creation of ZFS snapshots at specific intervals, apply a retention policy to them, and replicate them out to a remote system with ZFS, like a NAS with TrueNAS on it.

I run it in a FreeBSD jail and take frequent ZFS snapshots using zrepl. I’ve had to restore after failed updates and it worked flawlessly.

As others have noted, I use syncoid but zrepl is an alternative that could be considered.

I’m going to throw out Zrepl again because it’s amazing: https://zrepl.github.io/

Current idea: We offer some form of container each other, where we have that zvol mounted somewhere for the replication use. This would mean that I could create an "inside zfs" where I create a filebased zpool. How is performance on a filebased zpool? (Although it is technically not so important that it performs critically, just trying to find the - or one of - "best" ways). Then we would offer each an ssh endpoint into that container (It doesn't have to be ssh, but it is so far convenient to setup and resilient to be open to the public). And my current plan is to use zrepl (https://zrepl.github.io/) to organise replication from my home server to this "inside" zpool.

Try this awesome tool https://github.com/adnanh/webhook and you can make any bot you wish

Something like this: https://github.com/adnanh/webhook for a low code solution. This is the just the top hit, there tons of “Linux WebHook receivers” out there. Container A has the WebHook config to run ffmpeg. Container B runs curl to trigger the WebHook. Can be instrumented with fairly simple shell script.

If all you need is a Webhook trigger, you might want to take a look at https://github.com/adnanh/webhook

I thought this is for receiving webhooks at first glance, like another alternative for node-red, n8n.io, and adnanh/webhook.

you can register a webhook on github and listen to it from your second pc using https://github.com/adnanh/webhook

I occasionally trigger playbooks using this simple go project https://github.com/adnanh/webhook.

You can do a hell of a lot with webhooks, a bit of scripting and, err, webhook.

I use https://github.com/adnanh/webhook to deploy the changes in the git repository to the server and have it run docker compose up -d. I actually just modified it this week to run the docker commands in a background queue using https://vicerveza.homeunix.net/~viric/soft/ts/ (commands are added to a queue and run in the order they were added, useful for long-running commands) this way webhook can reply that the git repository was updated on the server and the docker compose command was added to the task queue and webhook doesn't timeout.