Portabase 1.29 / Agent 1.19: database configuration from the dashboard, MongoDB SRV support and file availability checks

[u/Dense_Marionberry741]

Hi everyone,

We’ve just released Portabase 1.29 and Agent 1.19, with another round of improvements focused on configuration, reliability and reducing the amount of manual setup required.

Repository: https://github.com/Portabase/portabase

Quick recap if you’re new to Portabase:

Portabase is an open-source, self-hosted backup and restore platform designed for data retention, disaster recovery and homogeneous database migrations. It uses a central dashboard with lightweight agents deployed close to your databases and workloads.

We currently support 9 database engines (PostgreSQL, MySQL, MariaDB, MongoDB, SQLite, Redis, Valkey, Firebird SQL and Microsoft SQL Server) as well as Docker volume backups.

What’s new in Portabase 1.29 / Agent 1.19

• Database configuration directly from the dashboard
  • Until now, databases were mainly declared through the agent's databases.json configuration.
  • You can now add and configure databases directly from the Portabase dashboard. databases.json remains supported, so both approaches can be used depending on how you prefer to manage your infrastructure.
• File availability checks
  • Portabase now checks whether backup files are actually still available in the configured storage.
  • If a file has been deleted, moved, or is otherwise unavailable, it is now marked as unavailable instead of being presented as a valid restore candidate.
• MongoDB SRV support
  • Agent 1.19 adds support for MongoDB SRV connections, making it easier to connect to MongoDB deployments using mongodb+srv://, including managed/cloud MongoDB environments.
• Various bug fixes and reliability improvements across the dashboard and agent.

What’s next

We’re now working on several areas:

• Deploying a public Portabase demo
• Improving and restructuring the documentation
• Enhancing the agent retry and resilience system
• Additional dashboard UX/UI improvements
• A database-specific options system, allowing advanced parameters to be configured for each supported engine
• Audit logs across the ecosystem for better traceability

As usual, feedback is welcome. If you find bugs, have trouble with the new dashboard-based configuration, or need database-specific options we don’t support yet, feel free to open an issue or discussion.

Thanks!

 

[u/asimovs-auditor]

Expand the replies to this comment to learn how AI was used in this post/project.

[u/ExerciseConscious334]

Finally you can add databases from the dashboard without messing with json configs, that was getting old fast

[u/Dense_Marionberry741 → u/ExerciseConscious334]

Yes, and JSON config is still available. You now have both options, and they work in parallel.