* Replace "Element" with "Element Web" - If Element indicates the web application, then it is changed to Element Web. - If it indicates clients branded with Element such as Element desktop, web, mobile clients, then it is changed to Element clients. - If it is combined with location sharing functionality, it is not changed. with other some changes, including: - Change "app.element.io" anchor link to "https://github.com/element-hq/element-web" on README.md, following other documentation files Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org> * Replace "SchildiChat" with "SchildiChat Web" - If SchildiChat indicates the web application, then it is changed to SchildiChat Web. - If it indicates clients branded with SchildiChat such as SchildiChat desktop, web, mobile clients, then it is changed to SchildiChat clients. - If it is combined with location sharing functionality, it is not changed. Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org> * Rename configuring-playbook-client-schildichat.md to configuring-playbook-client-schildichat-web.md Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org> * Rename configuring-playbook-client-element.md to configuring-playbook-client-element-web.md Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org> --------- Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org> Co-authored-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
2.9 KiB
Configuring Conduit (optional)
By default, this playbook configures the Synapse Matrix server, but you can also use Conduit.
Notes:
-
You can't switch an existing Matrix server's implementation (e.g. Synapse -> Conduit). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet.
-
homeserver implementations other than Synapse may not be fully functional. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding
Adjusting the playbook configuration
To use Conduit, you generally need to add the following configuration to your inventory/host_vars/matrix.example.com/vars.yml
file:
matrix_homeserver_implementation: conduit
Creating the first user account
Since it is difficult to create the first user account on Conduit (see famedly/conduit#276 and famedly/conduit#354) and it does not support registering users (via the command line or via the playbook) like Synapse and Dendrite do, we recommend the following procedure:
- Add
matrix_conduit_allow_registration: true
to yourvars.yml
the first time around, temporarily - Run the playbook (
ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
- see Installing) - Create your first user via Element Web or any other client which supports creating users
- Get rid of
matrix_conduit_allow_registration: true
from yourvars.yml
- Run the playbook again (
ansible-playbook -i inventory/hosts setup.yml --tags=setup-conduit,start
would be enough this time) - You can now use your server safely. Additional users can be created by messaging the internal Conduit bot
Configuring bridges / appservices
Automatic appservice setup is currently unsupported when using Conduit. After setting up the service as usual you may notice that it is unable to start.
You will have to manually register appservices using the the register-appservice command.
Find the registration.yaml
in the /matrix
directory, for example /matrix/mautrix-signal/bridge/registration.yaml
, then pass the content to Conduit:
@conduit:example.com: register-appservice
```
as_token: <token>
de.sorunome.msc2409.push_ephemeral: true
hs_token: <token>
id: signal
namespaces:
aliases:
- exclusive: true
regex: ^#signal_.+:example\.org$
users:
- exclusive: true
regex: ^@signal_.+:example\.org$
- exclusive: true
regex: ^@signalbot:example\.org$
rate_limited: false
sender_localpart: _bot_signalbot
url: http://matrix-mautrix-signal:29328
```