Hey everyone, I’m working on an Umbraco installer script for Proxmox. The script will be published on https://community-scripts.org/scripts. During installation, the user can currently choose between PostgreSQL (with the community package) or SQLite. Both options work fine. PostgreSQL runs very light inside an LXC container, and remote connections work as well. However, the maintainers commented on my pull request: “Either take SQLite or Postgres, no need for a user choice here.” So I’m wondering: which one would you choose?

Probably err on the side of caution and SQLite.. as

Umbraco ​C​M​S - ​Persistence - ​Postgre​S​Q​L -- ATTENTION: This is a community driven project and is not officially supported by Umbraco HQ.

Though can see value in PostgreSql too, and what about an external SQL provision? (LocalDB, SqlExpress, Sql, Azure Sql) ?? So maybe not a binary choice.. SQLite is usually for local development for Atomic Portability.. whereas Sql, AzureSql or PostrgeSql more on the production side? Another thought if this is a umbraco cloud local instance, is postgreSql supported for uda/content syncing via deploy? Sorry if I'm missing the intention for the Promox requirement... 🙂

It would be great if Umbraco eventually decides to officially support or adopt this PostgreSQL database provider. SQL Server can also be installed using a different script, but its system requirements are significantly higher (around 2 GB of memory). In contrast, the current LXC container runs perfectly fine with only 500 MB of RAM. These scripts are mainly used in homelab environments, so they are intended for hobby use rather than production. Additionally, the Umbraco source code can be published directly from Visual Studio to the LXC container via FTP, which makes the deployment workflow very simple and hobby‑friendly. Another important point: SQL Server 2025 does not run reliably on the latest Linux kernels used in Proxmox, which makes it even less suitable for lightweight LXC setups. PostgreSQL, on the other hand, runs extremely well in this environment.

Perhaps push back then on the maintainers comment.. explaining that it's not just a binary choice and either will do, there is a specific use case? hopefully this package opens the door to other persistence layers.. MySql / MariaDb.. maybe even no sql implementations?

SQLite is officially supported, Postgres is not. Umbraco will move to entity framework in the near future, which enabled many more database providers. But that is not yet the case. It's very much possible that third party packages won't work with Postgres if they don't take it into consideration.

for now i am taking the official route; SQLite. The third party packages is a good one to take account. I testen uSync and the 'Clean ​Starter ​Kit for ​Umbraco' and those nuget packages worked with PostgreSQL.. The development setup should be created in another project, so you can develop and publish to the LXC. Maybe with github actions or something.