cqrenet/matrix-docker-ansible-deploy
3
0
Fork 0
mirror of https://github.com/spantaleev/matrix-docker-ansible-deploy.git synced 2025-10-24 17:13:23 +00:00
Code Issues Wiki Activity
Files
f541425a7f48d4bffeedbcad89e5b632f4d8740d
matrix-docker-ansible-deploy/docs/configuring-playbook-appservice-double-puppet.md
Suguru Hirahara 0710298030 Update docs: remove descriptions about the ensure-matrix-users-created 
Apparently ensure-matrix-users-created is relevant only for components registered to "matrix_user_creator_users_auto" on group_vars/matrix_servers.

Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
2025-03-15 09:58:43 +02:00

2.5 KiB
Raw Blame History

Setting up Appservice Double Puppet (optional)

The playbook can install and configure the Appservice Double Puppet service for you. It is a homeserver appservice through which bridges (and potentially other services) can impersonate any user on the homeserver.

This is useful for performing double-puppeting via the appservice method. The service is an implementation of this approach.

Previously, bridges supported performing double-puppeting with the help of the Shared Secret Auth password provider module, but this old and hacky solution has been superseded by this Appservice Double Puppet method.

Adjusting the playbook configuration

To enable the Appservice Double Puppet service, add the following configuration to your inventory/host_vars/matrix.example.com/vars.yml file:

matrix_appservice_double_puppet_enabled: true

Extending the configuration

There are some additional things you may wish to configure about the service.

Take a look at:

  • roles/custom/matrix-appservice-double-puppet/defaults/main.yml for some variables that you can customize via your vars.yml file. You can override settings (even those that don't have dedicated playbook variables) using the matrix_appservice_double_puppet_registration_configuration_extension_yaml variable

Installing

After configuring the playbook, run it with playbook tags as below:

ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start

The shortcut commands with the just program are also available: just install-all or just setup-all

just install-all is useful for maintaining your setup quickly (2x-5x faster than just setup-all) when its components remain unchanged. If you adjust your vars.yml to remove other components, you'd need to run just setup-all, or these components will still remain installed. Note these shortcuts run the ensure-matrix-users-created tag too.

Usage

Installing the service will automatically enable double puppeting for all bridges that support double puppeting via the appservice method.