Problem
With upstream Weblate, the operator’s settings-override.py must not break Weblate’s own settings. It should load in a production-style image, keep upstream defaults (including WEBLATE_FORMATS), and register this plugin’s Django app so it can coexist with other plugins.
Acceptance Criteria
Implementation Notes
Replace a fragile hand-maintained override with a generated settings_override.py that extends WEBLATE_FORMATS safely and wires INSTALLED_APPS / WEBLATE_ADD_APPS so boost_weblate is registered correctly. Add tests for the override behavior. Validate with both pip install -e . and pip install . in the Weblate image. Separate follow-up: ensure AppConfig in apps.py is the canonical discovery path if you tighten Django app metadata.
References
- Related files:
settings-override.py
Problem
With upstream Weblate, the operator’s
settings-override.pymust not break Weblate’s own settings. It should load in a production-style image, keep upstream defaults (includingWEBLATE_FORMATS), and register this plugin’s Django app so it can coexist with other plugins.Acceptance Criteria
WEBLATE_FORMATSlist contains the plugin's custom formats alongside all upstream formats after the override is appliedImplementation Notes
Replace a fragile hand-maintained override with a generated
settings_override.pythat extendsWEBLATE_FORMATSsafely and wiresINSTALLED_APPS/WEBLATE_ADD_APPSsoboost_weblateis registered correctly. Add tests for the override behavior. Validate with bothpip install -e .andpip install .in the Weblate image. Separate follow-up: ensureAppConfiginapps.pyis the canonical discovery path if you tighten Django app metadata.References
settings-override.py