Hi community,

I’m one of the maintainers of Portabase, I shared it here for the first time two weeks ago and I have now some updates!

After an initial request from a community user in mid-January, and a few more along the way, we’ve finally added support for Firebird SQL. It seems to have a solid community behind it even though I hadn’t heard of it before.

Quick recap : Portabase is an open-source platform for database backup and restore.

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

So it now we support 8 databases: PostgreSQL, MariaDB, MySQL, SQLite, MongoDB, Redis, Valkey and Firebird SQL

What’s new in version 1.10:

  • Support for Firebird SQL (obviously)
  • Healthchecks for both the database and the agent (with optional notifications)
  • End-to-end tests to prevent regressions (coverage is still light, but we’re working on it)

What’s coming next:

  • Support for Microsoft SQL Server

If you’re using Firebird SQL (or any other supported database), we’d really appreciate your feedback. Feel free to open issues if you find any bugs.

  • aegg@europe.pub
    link
    fedilink
    English
    arrow-up
    2
    ·
    4 天前

    Looks very interesting, will try this out. pg_dump and restore stresses me out

    • KillianLarcher@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      4 天前

      Thanks! PostgreSQL is well supported (it was the first database implemented). Feel free to open an issue on GitHub if you want to suggest any improvements.

    • KillianLarcher@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      3
      ·
      4 天前

      Hi, Portabase handles database backup and restoration. It does not manage the migration process, so it depends on the type of database and whether migration is handled automatically or not.

      • amateurcrastinator@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        2 天前

        So to jump on this question because I am also interested: I can use this to create a backup of database version x and migrate to y and the backup again. Or if migrating goes bad restore x from backup

        • KillianLarcher@lemmy.worldOP
          link
          fedilink
          English
          arrow-up
          1
          ·
          20 小时前

          Yes, this is one of the common use cases.

          You can back up version X and perform the migration to version Y. If anything goes wrong during the migration, you can simply restore version X from the initial backup (you will, of course, need to downgrade to the original database version before restoring).