Changes needed for next release

[rolandgeider]

Hi! As a warning, the next version will need a new service to support offline mode on the mobile app. I'm not sure when this will be released, but most of the things work.

The deployment changes that are probably important to you are in #94, but basically:

• New powersync service
• wal_level=logical for postgres
• update the nginx/Caddy config, but just reverse proxy everything arriving at "/ps" to the new service
• new config options, JWT_PUBLIC_KEY and JWT_PRIVATE_KEY (docker compose exec web ./manage.py generate-jwt-keys)
• Set the db password in PS_DATABASE_URI in the usual format postgres://<user>:<password>@<host>:<port>/<dbname>. The old DJANGO_DB_DATABASE, etc can/should be removed (but don't need to) as django also reads the new one

To test this you can checkout feature/more-allauth for the backend and feature/allauth for the mobile app ("allauth" because there were some changes to the auth flow that impacted the sync as well, but I didn't want to merge. Also note that I'll probably rebase these branches in the future, just do a reset --hard)

Here's an overview of how the service operates.

(will try to complete the list these days)

[bbkz]

Thank you for the notification, i highly appreciate it.

I'll still have to look into it in more details and may have some questions. I mostly wonder about the

dev-postgres/initdb

scripts. Is this only a dev thing or are they ment to setup the powersync database?

[rolandgeider]

no, no, the initdb folder is just a bit of data massaging for development