[x] PR title descriptive (can be used in release notes)
Description
Bump API version to 1.5.1
Fix issue where local api connection failing (SSL not enabled locally)
Review Notes
The updates have already been deployed to the server along with updates from #2296, so this PR is more just for reference.
It should now at least be possible to check the updates from #2296 on a live server (if using a deployment that has user backup/restore and been recently updated to include code)
Dev Notes
I'm assuming the reason now that errors were being seen is either changes to the auto-update on postgres (pinned as v13 but could have included in minor patch), or to the API packages themselves (been a while since we've pushed server changes and remember a few non-deployed from #2270
The error message seen was no pg_hba.conf entry for host (with various ip/db name combinations following), as described in https://github.com/docker-library/postgres/issues/482. Most solutions seemed to suggest updating postgres data files to support connection from any source, however this wasn't easy to implement as the postgres data files are mapped to a docker volume and not easily editable (like example that maps to local disk). So instead I managed to find a fix that forces NestJS to connect to the database using SSL instead.
Git Issues
Closes #
Screenshots/Videos
If useful, provide screenshot or capture to highlight main changes
PR Checklist
Description
1.5.1Review Notes
The updates have already been deployed to the server along with updates from #2296, so this PR is more just for reference.
It should now at least be possible to check the updates from #2296 on a live server (if using a deployment that has user backup/restore and been recently updated to include code)
Dev Notes
I'm assuming the reason now that errors were being seen is either changes to the auto-update on postgres (pinned as
v13but could have included in minor patch), or to the API packages themselves (been a while since we've pushed server changes and remember a few non-deployed from #2270The error message seen was
no pg_hba.conf entry for host(with various ip/db name combinations following), as described inhttps://github.com/docker-library/postgres/issues/482. Most solutions seemed to suggest updating postgres data files to support connection from any source, however this wasn't easy to implement as the postgres data files are mapped to a docker volume and not easily editable (like example that maps to local disk). So instead I managed to find a fix that forces NestJS to connect to the database using SSL instead.Git Issues
Closes #
Screenshots/Videos
If useful, provide screenshot or capture to highlight main changes