Load the local hostname's config, where possible #2071
+15
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This change mirrors some nice but niche behaviour from Element, wherein
config.$HOSTNAME.json
is tried beforeconfig.json
.This is very handy, at least for me, because I serve cinny from a multitude of domains, but all from the same dist directory. This means if you visit cinny from one of my domains that is for a different homeserver, you will get the config for only one of my homeservers.
An example of this is https://cinny.transgender.ing - the
config.json
is loaded, which is intended for https://cinny.nexy7574.co.uk. Element, however, nicely tries to loadconfig.element.transgender.ing.json
in the first case, meaning I can serve a different default login server.Type of change
Checklist: