From 15d972e26fa3e5295da64b416a40f1130edbd41b Mon Sep 17 00:00:00 2001 From: alexbelgium Date: Fri, 4 Sep 2026 20:17:41 +0200 Subject: [PATCH] docs(wger): use the ISO date format the rest of this CHANGELOG uses The 2.6.4 heading was written 04-09-2026 while every other dated heading in this file, and 22937 of the 23999 dated headings in the repo, use ISO YYYY-MM-DD. Copilot flagged the inconsistency on #3044. Co-Authored-By: Claude Opus 5 --- wger/CHANGELOG.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/wger/CHANGELOG.md b/wger/CHANGELOG.md index b7a77bb10d..ee359908df 100644 --- a/wger/CHANGELOG.md +++ b/wger/CHANGELOG.md @@ -1,4 +1,4 @@ -## 2.6.4 (04-09-2026) +## 2.6.4 (2026-09-04) - Fix the add-on failing to start on a fresh install with `django.core.exceptions.ImproperlyConfigured: Set the DJANGO_DB_ENGINE environment variable`. The upstream `wger/server` image stopped shipping database defaults, and `settings/main.py` reads `DJANGO_DB_ENGINE` and `DJANGO_DB_DATABASE` with no fallback, so the add-on now sets them explicitly to sqlite at `/data/database.sqlite` — the same location the previous startup rewrite produced, so existing databases keep working. - Set `DJANGO_PERFORM_MIGRATIONS=True`, as upstream's own docker deployment does, so an existing database gets new migrations applied when the add-on is rebuilt against a newer upstream release.