There's an ongoing feature request about recurrence on the Nextcloud github. There was mention that using a client that supports it is no problem, but to be careful not to mark a task as complete on the web UI, as that would remove the entire task instead of marking one repetition as complete.
Is there a specific reason you're taking the services down before bringing them back up? Just docker compose pull && docker compose up -d recreates all services that had a new image pulled, but leaves the others running.
I like this perspective of yours, and while I don't think I'll join you on your instance (I take it this was an open invitation, yes?), I'll look into ways to hide votes on my client.
Although I do wonder, would you prefer everyone to return to long strings of "+1" and "agreed" posts?
... and enhanced by a sentence or two why it is worthwhile. Getting really tired of the no-effort link drops around here. Better yet, the same no-effort link drop to multiple similar communities on various instances.
Is there a block function for link-only posts?
Are there filters to prevent seeing duplicate content?
I have done a similar thing in the past, but to flash firmware onto any device with a certain USB descriptor that gets plugged in. It was a mess of USB hubs and cables, but it worked.
What I did was write a udev rule that checks for the vendor and product id of a newly plugged in device and calls a script when there's a match. The script then performs the flashing and logs the output.
In your case:
dd the source USB to a file (make sure the partition you're dding is smalled than any target drive
Udev rule according to your needs (all the same product or different drives?)
Script that dds the file you created earlier back to the newly plugged in drive.
Wireguard, even though they explicitly mention it in their tutorials, doesn't have an allow/block list for me, so I can't allow the proxy network bridge. Curious those settings are gone. Too bad!
Sure, I'd subscribe to one.