From 73e8a7a0d7987a10654941b439d433ce32e2480e Mon Sep 17 00:00:00 2001 From: BirdNET-Go Addon Builder Date: Tue, 20 Oct 2026 22:01:30 +0200 Subject: [PATCH] wger: README, say when /ps/ is unrouted and when wger refuses to start (#3134) Co-Authored-By: Claude Opus 5.5 --- wger/CHANGELOG.md | 1 + wger/README.md | 11 +++++++++-- 2 files changed, 10 insertions(+), 2 deletions(-) diff --git a/wger/CHANGELOG.md b/wger/CHANGELOG.md index 3b259b9e56..e58ceabead 100644 --- a/wger/CHANGELOG.md +++ b/wger/CHANGELOG.md @@ -1,6 +1,7 @@ ## 2.8.0-dev.1.3 (2026-10-20) - Fix the PowerSync SQLite import failing with `CommandError: Unknown model: admin.logentry`, which kept wger from starting. wger does not install Django's admin app, so the import no longer asks `dumpdata` to exclude its log table (#3134). +- README: correct when `/ps/` stays unrouted and when wger still starts. A wrong `wal_level` is detected only after wger is up, so `/ps/` then answers 502 rather than being unrouted (#3134). ## 2.8.0-dev.1.2 (2026-10-19) diff --git a/wger/README.md b/wger/README.md index d3e5dd0815..d6d7caa96e 100644 --- a/wger/README.md +++ b/wger/README.md @@ -211,8 +211,15 @@ reason other than `wal_level`, the add-on log carries PowerSync's own error. With everything in place the add-on log reports the PowerSync URL, and `/ps/probes/liveness` answers instead of logging `Not Found: /ps/probes/liveness`. -If a prerequisite is missing the add-on still starts wger normally and the log says -exactly which variable is wrong; `/ps/` stays unrouted in that case. +If a variable is missing or invalid, the log says exactly which one and `/ps/` stays +unrouted. wger itself still starts, unless `PS_DATABASE_URI` points at Postgres while +there is SQLite data waiting to be imported: then it refuses to start, so the empty +Postgres database is not set up as a new instance. Fix the variable, or remove +`PS_DATABASE_URI` to go back to SQLite. + +The `wal_level` check and the PowerSync storage setup only run once wger is up, after +`/ps/` is already routed. If either fails, the log says so, PowerSync is not started, +and `/ps/` answers `502 Bad Gateway` until you fix the cause and restart the add-on. If you put your own reverse proxy in front of the add-on, nothing extra is needed: the `/ps/` route forwards an incoming `X-Forwarded-Proto` unchanged and only falls back to