Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Server/updates 1.5.0 #2318

Merged
merged 4 commits into from
Jun 4, 2024
Merged

Server/updates 1.5.0 #2318

merged 4 commits into from
Jun 4, 2024

Conversation

chrismclarke
Copy link
Member

@chrismclarke chrismclarke commented May 8, 2024

PR Checklist

  • 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

Copy link
Collaborator

@esmeetewinkel esmeetewinkel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can confirm dynamic data is coming through on the server as expected
image
with values of the form {"data_list": {"comp_data_items_list": {"id_1": {"id": "id_1", "_id": "id_1", "label": "Task 1", "_index": "@item._index + 1", "completed": false}, "id_2": {"id": "id_2", "_id": "id_1", "label": "Task 2", "_index": "0", "completed": true}}, "comp_task_prog_bar_dyn_data": {"id_1": {"id": "id_1", "completed": false, "row_index": 0}, "id_2": {"id": "id_2", "completed": false, "row_index": 1}, "id_3": {"id": "id_3", "completed": true}, "id_4": {"id": "id_4", "completed": true}, "id_5": {"id": "id_5", "completed": true}}}}

I am also able to import data from one user into another

@esmeetewinkel esmeetewinkel merged commit ab1b0ee into master Jun 4, 2024
6 checks passed
@esmeetewinkel esmeetewinkel deleted the server/updates-1.5.0 branch June 4, 2024 08:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants