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.<your-domain>/_matrix/maubot/

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

Adjusting the playbook configuration

Add the following configuration to your inventory/host_vars/matrix.DOMAIN/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.

Installing

After configuring the playbook, run the installation command again (just install-all):

Notes:

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.

Usage

You can visit matrix.<your-domain>/_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)

Server service management

If you need to do stop and start manually of the Maubot service, you can use systemd command systemctl or just.

systemctl : You will need to ssh insto the server and you can then issue systemctl restart matrix-bot-maubot as root.
just : You can run the command from where the ansible playbook is run(probably from your laptop). just stop-group bot-maubot and just start-group bot-maubot.

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 can only use Obtain an access token via curl and not Obtain an access token via Element. By getting the access token via Element will give your bot issue with Encrypted room. Read more.

3.3 KiB Em bruto Responsabilidade Histórico