App settings interfere

[nesnoj]

If more than one app use the same settings variables, they conflict (last loaded app rules).

Current problem in FRED: rl-institut/WAM_APP_FRED#49

Reason: The WAM reads the settings.py of each app which mays contain module config stuff like this one. So it's not a per-app config but a global (module) one.

This is a general WAM issue we have to solve!
Ideas, @henhuy ?

[henhuy]

I will write a WAM-function for adding new packages, which will check for duplicates.
This function should be called in settings.py or app_settings.py (not sure yet).

[nesnoj]

Your PR solves the multiple app problem but we still have the settings' var overwrite problem.
@henhuy Do you have a good idea to solve this without workarounds for single apps (e.g. for leaflet as mentioned in rl-institut/WAM_APP_FRED#49) ?

As packages such as django-leaflet expect specific config variables in the settings, we neither can put the app-specific vars e.g. in a dict nor rename them without package forks...

[nesnoj]

I implemented a solution for this specific django-leaflet-related issue in rl-institut/WAM_APP_stemp_abw#66 using a simple settings override. Everything's fine for now.

But this does not not solve the general problem of conflicting settings. Right now this makes the WAM quite fragile and we cannot detect those problems via automated tests, only manually.

Also, there's the same problem with the templates #12.

Sounds like another reason for a WAM circle ;)