Setting up maubot (optional)

The playbook can install and configure maubot for you.

After setting up maubot, you can use the web management interface to make it do things. The default location of the management interface is matrix.example.com/_matrix/maubot/

See the project’s documentation to learn what it does and why it might be useful to you.

Adjusting the playbook configuration

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

matrix_bot_maubot_enabled: true

# Uncomment and adjust this part if you'd like to use a username different than the default
# matrix_bot_maubot_login: bot.maubot

# Generate a strong password here. Consider generating it with `pwgen -s 64 1`
matrix_bot_maubot_initial_password: PASSWORD_FOR_THE_BOT

matrix_bot_maubot_admins:
  - yourusername: securepassword

You can add multiple admins. The admin accounts are only used to access the maubot administration interface.

Adjusting the maubot URL

By default, this playbook installs maubot on the matrix. subdomain, at the /_matrix/maubot/ path (https://matrix.example.com/_matrix/maubot/). This makes it easy to install it, because it doesn’t require additional DNS records to be set up. If that’s okay, you can skip this section.

By tweaking the matrix_bot_maubot_hostname and matrix_bot_maubot_path_prefix variables, you can easily make the service available at a different hostname and/or path than the default one.

Example additional configuration for your inventory/host_vars/matrix.example.com/vars.yml file:

# Change the default hostname and path prefix
matrix_bot_maubot_hostname: maubot.example.com
matrix_bot_maubot_path_prefix: /

Adjusting DNS records

If you’ve changed the default hostname, you may need to adjust your DNS records to point the maubot domain to the Matrix server.

See Configuring DNS for details about DNS changes.

If you’ve decided to use the default hostname, you won’t need to do any extra DNS configuration.

Installing

After configuring the playbook and potentially adjusting your DNS records, run the playbook with playbook tags as below:

ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start

Notes:

The ensure-matrix-users-created playbook tag makes the playbook automatically create the bot’s user account.
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.
If you change the bot password (matrix_bot_maubot_initial_password in your vars.yml file) subsequently, the bot user’s credentials on the homeserver won’t be updated automatically. If you’d like to change the bot user’s password, use a tool like synapse-admin to change it, and then update matrix_bot_maubot_initial_password to let the bot know its new password.

Usage

By default, you can visit matrix.example.com/_matrix/maubot/ to manage your available plugins, clients and instances.

You should start in the following order

Create one or more clients: A client is a Matrix account which the bot will use to message. By default, the playbook creates a bot.maubot account (as per the configuration above). You only need to obtain an access token for it
Upload some Plugins: Plugins can be obtained from here or any other source.
Create an instance: An instance is the actual bot. You have to specify a client which the bot instance will use and the plugin (how the bot will behave)

Obtaining an access token

This can be done via mbc login then mbc auth (see the maubot documentation). To run these commands, you’ll first need to exec into the maubot container with docker exec -it matrix-bot-maubot sh.

Alternatively, you can follow our generic obtain an access token documentation. Be aware that you’d better use the Obtain an access token via curl method (not Obtain an access token via Element Web) as the latter will give your bot issues in encrypted rooms. Read more.

5.0 KiB Ruw Blame Geschiedenis