Currently the primary storage for forum posts, user accounts etc. is the postgres database.
May I suggest please to make the main storage format for forum contents simple text files?
Due to hard to fix database issues (difficult for me, as user), I think the risk is high for losing all forum data because of the seemingly/effectively opaque binary format of SQL databases. Looks like nobody can fix a severely broken database (which won’t be a visible problem as above issue) or too expensive for laymen.
I am sure, there are very good reasons to use databases such as postgres such as performance. However I propose a transparent human readable text format for backups as an emergency last resort in case db backup and restore functionality is corrupt or broken.
You probably don’t need to be convinced how amazing git is, you’re already using that. Forum contents could be stored as sub folders in and lots of text files. Thereby the whole folder could be put under git version control. If any bugs are introduced, it’s much easier to track down what commit caused it.
Since databases (unreliable, complex) are probably still be required, these text files (simple, reliable) could serve as a template to re-create the database “from source”. If storage of new posts inside text files is too slow in realtime, you can make the text file backup option on-demand or when the system is idle. (Delayed write / write cache.)
Public data (public forum posts) would be in a different folder than private user data, hashed passwords. Added advantage would be that the public part (posts) could even be published on a git remote for those who find that useful (archival). User data would stay in a local-only git repository (or custom, remote, private, encrypted git repository).