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.

This looks exciting! A couple of questions:

1. How would I deploy an agent into an existing docker container in a way that makes it persist across restarts? Most of my databases are running in containers.
2. Regarding redis and valkey: what good does backup do without restore? Not trying to denigrate; I just really want to understand how that is useful.

Thanks for building this!

Not many… but this community isn’t for those people. It’s for people who are already predisposed to self-hosting software.

Couldn’t the same be said for just about any self-hosted app? You can watch video files with a local video player, so no need for Jellyfin; you can save passwords in KeePass, so no need for Vaultwarden; etc.

Seems to me like, if you’d like to have access to this app along with your data from any computer without having to overlay a separate data syncing solution and install a local app on each of those computers, that’s justification enough. Or maybe I’m just not understanding your critique here…