Checked
Which addon?
Wger 2.6.3
Is your feature request related to a problem? Please describe
The official Wger Android/Flutter app (2.0.3+) requires a PowerSync service (https://powersync.com/) for offline sync, in addition to the Django backend. After a successful login (password auth works fine, and JWT keys were manually generated via manage.py generate-jwt-keys since the addon doesn't set these by default), the app fails with:
"Sync-Dienst nicht erreichbar - prüfe ob der PowerSync-Dienst korrekt läuft" (Sync service unreachable - check if the PowerSync service is running correctly)
The server log confirms the app is probing for a PowerSync liveness endpoint that doesn't exist:
Not Found: /ps/probes/liveness
No PowerSync service runs alongside the addon. PowerSync also only supports PostgreSQL, MongoDB, MySQL, or SQL Server as a source database for replication — not SQLite, which this addon currently defaults to (DJANGO_DB_ENGINE=django.db.backends.sqlite3).
I noticed the addon config already exposes Postgres-related env vars (DJANGO_DB_HOST, DJANGO_DB_PORT, DJANGO_DB_PASSWORD) even while DJANGO_DB_ENGINE is set to sqlite3 — suggesting Postgres support already exists as an option, just not currently the default/documented path.
I already run a standalone PostgreSQL 17 instance on my HAOS host that I'd be happy to point the addon at, if that helps make this easier to implement/test.
A similar gap was reported for the TrueNAS wger app: truenas/apps#5298 ("Need to add the PowerSync container / service upon deploying wger" — "This is required for the mobile app to work properly")
Describe the solution you'd like
Could the addon optionally bundle/support a PowerSync container (alongside a Postgres-backed Wger instance) so the current mobile app version works fully? Happy to help test against my existing Postgres 17 instance if there's a config direction you'd like to try.
Checked
Which addon?
Wger 2.6.3
Is your feature request related to a problem? Please describe
The official Wger Android/Flutter app (2.0.3+) requires a PowerSync service (https://powersync.com/) for offline sync, in addition to the Django backend. After a successful login (password auth works fine, and JWT keys were manually generated via manage.py generate-jwt-keys since the addon doesn't set these by default), the app fails with:
"Sync-Dienst nicht erreichbar - prüfe ob der PowerSync-Dienst korrekt läuft" (Sync service unreachable - check if the PowerSync service is running correctly)
The server log confirms the app is probing for a PowerSync liveness endpoint that doesn't exist:
Not Found: /ps/probes/liveness
No PowerSync service runs alongside the addon. PowerSync also only supports PostgreSQL, MongoDB, MySQL, or SQL Server as a source database for replication — not SQLite, which this addon currently defaults to (DJANGO_DB_ENGINE=django.db.backends.sqlite3).
I noticed the addon config already exposes Postgres-related env vars (DJANGO_DB_HOST, DJANGO_DB_PORT, DJANGO_DB_PASSWORD) even while DJANGO_DB_ENGINE is set to sqlite3 — suggesting Postgres support already exists as an option, just not currently the default/documented path.
I already run a standalone PostgreSQL 17 instance on my HAOS host that I'd be happy to point the addon at, if that helps make this easier to implement/test.
A similar gap was reported for the TrueNAS wger app: truenas/apps#5298 ("Need to add the PowerSync container / service upon deploying wger" — "This is required for the mobile app to work properly")
Describe the solution you'd like
Could the addon optionally bundle/support a PowerSync container (alongside a Postgres-backed Wger instance) so the current mobile app version works fully? Happy to help test against my existing Postgres 17 instance if there's a config direction you'd like to try.