# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 9
# self = https://watcher.sour.is/conv/b2fdplq
I need to fully automate my backup/recovery process. I use restic as my primary backup/recovery tool and documented a process for Docker volume backup and restore with restic which I also use to backup Docker local volumes (_unfortuantely requires small amounts of downtime per service_) -- There is also this nice tool called auto-restic which I haven't gotten around to using yet, which I _thinik_ will help with automating. Right now I still kick the process of by-hand, whenever I feel I should probably do another backup 🤦♂️
I need to fully automate my backup/recovery process. I use restic as my primary backup/recovery tool and documented a process for Docker volume backup and restore with restic which I also use to backup Docker local volumes (_unfortuantely requires small amounts of downtime per service_) -- There is also this nice tool called auto-restic which I haven't gotten around to using yet, which I _thinik_ will help with automating. Right now I still kick the process of by-hand, whenever I feel I should probably do another backup 🤦♂️
I need to fully automate my backup/recovery process. I use restic as my primary backup/recovery tool and documented a process for Docker volume backup and restore with restic which I also use to backup Docker local volumes (_unfortuantely requires small amounts of downtime per service_) -- There is also this nice tool called auto-restic which I haven't gotten around to using yet, which I _thinik_ will help with automating. Right now I still kick the process of by-hand, whenever I feel I should probably do another backup 🤦♂️
One of my main problems/blockers I think is that I use my Mac Studio as my primary backup target (_from my NAS and Docker volumes_), then I use Backblaze B2 as my secondary target from there. So my backup process is 2-step with two targets (_a local target and a remote target_). What I really need is another secondary smaller NAS that I can just host the tools on more permanently, hmmm.
One of my main problems/blockers I think is that I use my Mac Studio as my primary backup target (_from my NAS and Docker volumes_), then I use Backblaze B2 as my secondary target from there. So my backup process is 2-step with two targets (_a local target and a remote target_). What I really need is another secondary smaller NAS that I can just host the tools on more permanently, hmmm.
One of my main problems/blockers I think is that I use my Mac Studio as my primary backup target (_from my NAS and Docker volumes_), then I use Backblaze B2 as my secondary target from there. So my backup process is 2-step with two targets (_a local target and a remote target_). What I really need is another secondary smaller NAS that I can just host the tools on more permanently, hmmm.
Woohoo 🥳 Finally fixed the remaining bugs in my set of shell scripts for backing up Docker volumes:
https://git.mills.io/prologic/backup-docker-volumes
Has the behavior of:
- Given a Docker node;
- Find all active volumes.
- For each volume, find its running container or service,
- Stop the Container or scale down the Service.
- Run the backup on the volume
- Restart the Container or scale up the Service.
Woohoo 🥳 Finally fixed the remaining bugs in my set of shell scripts for backing up Docker volumes:
https://git.mills.io/prologic/backup-docker-volumes
Has the behavior of:
- Given a Docker node;
- Find all active volumes.
- For each volume, find its running container or service,
- Stop the Container or scale down the Service.
- Run the backup on the volume
- Restart the Container or scale up the Service.
Woohoo 🥳 Finally fixed the remaining bugs in my set of shell scripts for backing up Docker volumes:
https://git.mills.io/prologic/backup-docker-volumes
Has the behavior of:
- Given a Docker node;
- Find all active volumes.
- For each volume, find its running container or service,
- Stop the Container or scale down the Service.
- Run the backup on the volume
- Restart the Container or scale up the Service.