Still figuring things out here. In the world, I mean.
- 🏡 Personal site: https://devon.lol/
- 🐭 Previous Lemmy profile: https://lemmy.ml/u/RadDevon
- 🦣 Mastodon: https://techhub.social/@RadDevon
- 📈 Tildes: https://tildes.net/user/RadDevon
Still figuring things out here. In the world, I mean.
Leaving Apple behind after 18 years
Permanently Deleted
Wireless keyboard disconnects when idle for ~2 minutes
Backups: Am I doing this right?
Updates vs. version pinning in Docker-based homelab
No HDR option in Bazzite/KDE after connecting computer directly to display
Keyboard customization in profile not working until manually sourced
Dealing with games that just won't run on Linux
Why do most gaming laptops have vents on the bottom?
Tiny Awards
Thanks for the clarification. By "persist across restarts," I'm referring to the fact that if I just install the agent in my container, it won't persist if I restart the container, unless I install it on a volume which seems clunky. Running the agent alongside in a separate container with network access is the solution I was looking for.
On the Redis and Valkey restores, that makes sense. Disaster recovery is my use case anyway. Do you document the manual restore process for those? I didn't notice it in a brief review of the docs, but I may have overlooked it.