To allow fully dynamic configuration we should move MULTISITE_CMS_URLS and MULTISITE_CMS_ALIASES to the database.
MULTISITE_CMS_ALIASES is trivial as django-multisite Alias already does the jobMULTISITE_CMS_URLS less so, as we need to add this information somewhere in the models and adding a model just for this, it looks very inefficient
All these information must be cached otherwise we will incur in a huge performance hit
To allow fully dynamic configuration we should move
MULTISITE_CMS_URLSandMULTISITE_CMS_ALIASESto the database.MULTISITE_CMS_ALIASESis trivial asdjango-multisiteAliasalready does the jobMULTISITE_CMS_URLSless so, as we need to add this information somewhere in the models and adding a model just for this, it looks very inefficientAll these information must be cached otherwise we will incur in a huge performance hit