mirror of
https://github.com/alexbelgium/hassio-addons.git
synced 2026-09-12 12:49:09 +02:00
* fix(wger): set the database env vars the upstream image stopped shipping wger/server:latest no longer defines DJANGO_DB_ENGINE or DJANGO_DB_DATABASE in its image environment, and upstream settings/main.py reads both with no fallback. Every fresh install therefore died at startup with "ImproperlyConfigured: Set the DJANGO_DB_ENGINE environment variable". Set both explicitly in the Dockerfile, pointing at the sqlite database in /data/database.sqlite that the add-on already persists, and add DJANGO_PERFORM_MIGRATIONS=True so an existing database picks up new migrations when the image is rebuilt against a newer upstream release. With the path now set through the environment, the cont-init rewrite of the database path in the Python settings is dead code — upstream no longer hardcodes /home/wger/db/database.sqlite anywhere, so it only logged a warning. Also move the add-on to the addon_configs location, as the issue asks: the shared 01-config_yaml.sh template migrates an existing /homeassistant/addons_config/wger/config.yaml on the first start. Fixes #3043 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * 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 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 <noreply@anthropic.com>