As suggested in #63 (Github issue), splitting the playbook's logic into multiple roles will be beneficial for maintainability. This patch realizes this split. Still, some components affect others, so the roles are not really independent of one another. For example: - disabling mxisd (`matrix_mxisd_enabled: false`), causes Synapse and riot-web to reconfigure themselves with other (public) Identity servers. - enabling matrix-corporal (`matrix_corporal_enabled: true`) affects how reverse-proxying (by `matrix-nginx-proxy`) is done, in order to put matrix-corporal's gateway server in front of Synapse We may be able to move away from such dependencies in the future, at the expense of a more complicated manual configuration, but it's probably not worth sacrificing the convenience we have now. As part of this work, the way we do "start components" has been redone now to use a loop, as suggested in #65 (Github issue). This should make restarting faster and more reliable.
1.7 KiB
Adjusting mxisd Identity Server configuration (optional)
By default, this playbook configures an mxisd Identity Server for you.
This server is private by default, potentially at the expense of user discoverability.
Matrix.org lookup forwarding
To ensure maximum discovery, you can make your identity server also forward lookups to the central matrix.org Identity server (at the cost of potentially leaking all your contacts information).
Enabling this is discouraged and you'd better learn more before proceeding.
Enabling matrix.org forwarding can happen with the following configuration:
matrix_mxisd_matrixorg_forwarding_enabled: true
Additional features
What this playbook configures for your is some bare minimum Identity Server functionality, so that you won't need to rely on external 3rd party services.
A few variables can be toggled in this playbook to alter the mxisd configuration that gets generated.
Still, mxisd can do much more. You can refer to the mxisd website for more details and configuration options.
To use a more custom configuration, you can define a matrix_mxisd_configuration_extension_yaml
string variable
and put your configuration in it.
To learn more about how to do this, refer to the information about matrix_mxisd_configuration_extension_yaml
in the default variables file of the mxisd component.
Troubleshooting
If email address validation emails sent by mxisd are not reaching you, you should look into Adjusting email-sending settings.