Make matrix_homeserver_implementation influence matrix_IMPLEMENTATION_enabled, not the other way around
Doing this seems more reasonable and simpler.
This commit is contained in:
@ -8,11 +8,13 @@
|
||||
matrix_domain: ~
|
||||
|
||||
# This will contain the homeserver implementation that is in use.
|
||||
# Example values: 'synapse', 'dendrite', etc.
|
||||
# You normally don't need to set this variable manually.
|
||||
# Its value is automatically set depending on the homeserver implementation that you have enabled via other variables
|
||||
# (e.g. `matrix_synapse_enabled`, `matrix_dendrite_enabled`, etc.)
|
||||
matrix_homeserver_implementation: ''
|
||||
# Valid values: synapse, dendrite
|
||||
#
|
||||
# By default, we use Synapse, because it's the only full-featured Matrix server at the moment.
|
||||
#
|
||||
# This value automatically influences other variables (`matrix_synapse_enabled`, `matrix_dendrite_enabled`, etc.).
|
||||
# The homeserver implementation of an existing server cannot be changed without data loss.
|
||||
matrix_homeserver_implementation: synapse
|
||||
|
||||
# This is where your data lives and what we set up.
|
||||
# This and the Element FQN (see below) are expected to be on the same server.
|
||||
|
Reference in New Issue
Block a user