The community.wordpress.org Matrix server relies on bots (non-human users) that perform a variety of tasks. Bots can react to messages or other events posted on Matrix, and/or post to Matrix whenever something happens.
Bots run in a bot engine called Maubot, which provides an Admin UI through which bots can be created and configured. Maubot bots are implemented in Python, and are known as Plugins. There is an ecosystem of existing plugins for Maubot, and custom plugins can be implemented as well.
This repository provides the following:
- Documentation on how to configure bots through Maubot's Admin UI
- The source code for custom plugins used in
community.wordpress.org - Local development environment to test, modify and create plugins
- Automation to produce the Docker image for
community.wordpress.org's Maubot instance - Documentation on how to redeploy Maubot so that it uses the latest docker image
Bots are configured through an Admin UI that is available to server maintainers. You can get a replica of that UI in your local machine, see development environment for instructions.
To effectively use the Admin UI, it's important to understand a few Maubot concepts. A Maubot bot is achieved by combining the following three things:
- Plugin: a Python module that implements the logic of the bot.
- Client: the Matrix user that the bot will use to post to Matrix, and to receive messages from Matrix.
- Instance: an instance ties a Plugin to a Client, and allows passing configuration to the Plugin. There can be multiple instances of the same Plugin, each potentially using a different Client, and specific configuration.
To use Maubot's CLI, you first need to set up a development environment.
Certain operations are easier to do through Maubot's CLI than through the Admin UI. An example of this is creating clients, since it's not possible to automatically retrieve an access token when creating a client through the Admin UI, but the CLI is capable of doing so.
You can access Maubot's CLI with:
bin/mbcWhen using the CLI, the first step is typically to log in to a Maubot instance, so that the CLI can control said instance. As part of the setup process of the development environment, the CLI has already been logged in to the local Maubot instance (wporg-local).
However, you can also log in to the production instance (provided you're a server maintainer, and have access to Maubot's admin password):
bin/mbc login \
--server https://wporg.automattrix.com \
--username admin \
--alias wporg-prodNotice we assigned the instance an alias of
wporg-prod. This allows you to usewporg-prodwhenever you need to pass the--serverargument to anybin/mbccommand.
You can see all Maubot servers you're logged-in to (and their aliases) with:
cat ~/.config/maubot-cli.jsonYou can create Maubot clients through the CLI, which will automatically set an access token for the client you're creating.
Note that the WordPress.org user must already exists, prior to attempting to create a client for it. If the WordPress.org user does not yet exists, you must first register an account like you would for any normal WordPress.org user.
The username of the WordPress.org user MUST end with
bot. For example, if you're creating a Foo Bot, its WordPress.org username MUST befoobot.
You can then create the Maubot client as follows:
Make sure to first log out from WordPress.org in your default browser (or be logged-in to the user for which you want to create a client for). The following command will initiate the OIDC flow in your default browser, and you don't want to accidentally use the wrong user.
# Replace the value for the --username argument with the Matrix username of the bot.
bin/mbc auth \
--server wporg-prod \
--update-client \
--homeserver community.wordpress.org \
--username examplebot \
--ssoOnce you complete the OIDC flow, a Maubot client will have been created in the Maubot Admin UI. Both the display name and the avatar will have been set to disable, but you should set correct values for them, through the Admin UI. If the username of the bot would be examplebot, its display name should be Example Bot.
To set an avatar, you must first upload the image to a public Matrix room (e.g. #matrix-testing:community.wordpress.org). You can then copy the URL from the room event (in Element: click the ... in the menu that appears when hovering the image in the timeline, then View source, then copy the value from content.url, it starts with mxc://).
You can set up a local development environment that allows you to do the following:
- Run a local instance of Maubot, along with a homeserver and a Matrix client. This is useful to test existing plugins or develop new ones.
- Use the Maubot CLI to talk to both the local and production Maubot instances. Note the production instance is only available to server maintainers.
Start by cloning the repository:
git clone [email protected]:WordPress/matrix-bots.git
cd matrix-botsDo initial setup:
makeFrom the repo root, run:
docker compose upThe first time you do this, Maubot will likely fail to start due to not being able to connect to Postgres. To fix this, wait for the matrix-bots-wporg-synapse container to say No more background updates, then restart all containers:
# ctrl-c to stop all containers, then:
docker compose upFinally, run the setup script:
bin/setupYou should now have the following services running:
synapse(Matrix server): http://localhost:8008element(Matrix client): http://localhost:8009 [user:admin, password:admin]maubot(Maubot's Admin UI): http://localhost:29316 [user:admin, password:admin]postgres(Database server):postgresql://postgres:postgres@localhost:5432
The homeserver domain is matrix-bots-wporg.local. An @admin Matrix user and a respective Maubot client should have been created. You can use that client to test and develop plugins.
Custom plugins are plugins that have been developed by the WordPress.org community. Their source code is contained in this repo (under plugins/), and they are made available to the production Maubot through the Docker image.
To develop custom plugins, you'll need a development environment running locally.
You can build a custom plugin and deploy it to the local Maubot instance with the following command (plugins/example is the path to the directory containing the plugin you want to build and deploy):
bin/build plugins/exampleThe local Maubot instance will automatically start using the newly-built version of the plugin.
TODO
If you wish to delete all containers and data, you can use the following script, which will restore the local checkout of the repository to its initial state, as if it had just been cloned:
bin/wipeThis repository provides the Docker image for community.wordpress.org's Maubot instance. The image is exactly the same as Maubot's official image, but with plugins placed in /data/plugins.
Since community.wordpress.org's Maubot instance does not (deliberately) allow uploading plugins through the Admin UI, the only plugins that will be available are the ones bundled into this Docker image.
To issue a new release of the image, edit the version file so that it contains the version you want to release. The versioning scheme used is: whatever Maubot's version is, with an extra decimal. For example, if Maubot's version (in Dockerfile) is v0.4.2, the version file would contain something like:
v0.4.2.0
Then commit the version file and push. A GitHub Action will then publish the Docker image to the GitHub Container Registry.
Redeploy of Maubot in production will be done by server maintainers when a new Docker image version is published.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent