Centralise the custom template directory (#10596)
Several configuration sections are using separate settings for custom template directories, which can be confusing. This PR adds a new top-level configuration for a custom template directory which is then used for every module. The only exception is the consent templates, since the consent template directory require a specific hierarchy, so it's probably better that it stays separate from everything else.
Showing
- changelog.d/10596.removal 1 addition, 0 deletionschangelog.d/10596.removal
- docs/SUMMARY.md 1 addition, 0 deletionsdocs/SUMMARY.md
- docs/sample_config.yaml 19 additions, 206 deletionsdocs/sample_config.yaml
- docs/templates.md 239 additions, 0 deletionsdocs/templates.md
- docs/upgrade.md 11 additions, 0 deletionsdocs/upgrade.md
- synapse/config/account_validity.py 6 additions, 1 deletionsynapse/config/account_validity.py
- synapse/config/emailconfig.py 25 additions, 46 deletionssynapse/config/emailconfig.py
- synapse/config/server.py 25 additions, 0 deletionssynapse/config/server.py
- synapse/config/sso.py 9 additions, 164 deletionssynapse/config/sso.py
- synapse/module_api/__init__.py 2 additions, 1 deletionsynapse/module_api/__init__.py
- synapse/rest/synapse/client/new_user_consent.py 2 additions, 0 deletionssynapse/rest/synapse/client/new_user_consent.py
- synapse/rest/synapse/client/pick_username.py 2 additions, 0 deletionssynapse/rest/synapse/client/pick_username.py
Loading
Please register or sign in to comment