Hi, thanks for the repo, deployed in my cluster now. Wanted to implement support for another databases but first wanted to ask

[lgemc]

Hi, no problems or issues at all, just here to say this project is very interesting and it is working very well on my cluster, thanks for that.

That said, would love to have the possibility to be connected to a postgres database (sure it must live in its own database abstraction to allow easy switch to postgres, mariadb, sqlite etc), it could simplify a lot my own work, my entire cluster is built over a k8s postgres instance.

If you do agree, i can implement this feature, test it and then send it as a pr but just wanted to ask first for any thoughts

[bifrost0x]

Hi @lgemc, thanks a lot for the suggestion - and sorry, I initially misunderstood your request. You are referring to PostgreSQL as an alternative backend for WebSSH's internal application database, not to database connections as a user-facing feature.

That makes sense, especially for Kubernetes-based deployments. I need to review the implications for migrations, backup/restore, configuration, and testing before deciding on the exact scope. I will come back with a more concrete proposal here. If the scope is a good fit, I would also be happy to coordinate a contribution with you.

Thanks again for raising this!

[bifrost0x]

Hi @lgemc,

I reviewed the current storage, migration, backup, and runtime architecture in more detail. I think PostgreSQL support is feasible and useful, but I would like to keep the initial scope deliberately narrow and production-safe.

I would be comfortable with a contribution that:

• keeps SQLite as the default
• adds PostgreSQL as an optional backend for new installations
• uses proper database migrations and tests both backends
• documents connection security, configuration, and external database backups

The initial scope should not include automatic SQLite-to-PostgreSQL migration, generic support for every SQL database, or Kubernetes HA. Active SSH state currently remains process-local, so PostgreSQL alone would not make WebSSH safe for multiple application workers.

One important requirement is that the existing backup command must never silently claim to create a complete backup when an external database is configured.

If this scope works for you, I would be happy to coordinate the implementation and review a contribution.