Hi community,
I’m one of the maintainers of Portabase, and this is my first time sharing about it on Lemmy.
Portabase is an open-source platform for database backup and restore.
It’s designed to be simple, reliable, and lightweight, without exposing your databases to public networks. It works via a central server and edge agents (like Portainer), making it perfect for self-hosted or edge environments.
It currently supports 7 databases:
PostgreSQL, MariaDB, MySQL, SQLite, MongoDB, Redis and Valkey
Repository: https://github.com/Portabase/portabase
(we hit 500 stars recently!)
Key features:
- Logical backups for PostgreSQL, MySQL, MariaDB, MongoDB, SQLite, Redis, Valkey
- Multiple storage backends: local filesystem, S3, Cloudflare R2, Google Drive
- Notifications via Discord, Telegram, Slack, webhooks, etc.
- Cron-based scheduling with flexible retention strategies
- Agent-based architecture for secure, edge-friendly deployments
- Ready-to-use Docker Compose setup and Helm Chart
What’s coming next:
- Increasing test coverage
- Extending database support
I’d love to hear from you: which database would you like to see supported next in Portabase?
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.