Because enabling the native E2EE support requires the clean access token obtained with curl, which is supposed to be specified to "matrix_bot_draupnir_access_token", setting "matrix_bot_draupnir_enable_experimental_rust_crypto" to true means that "matrix_bot_draupnir_access_token" is also specified.
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
The setting is required, and it is not friendly to split the required settings with optional ones.
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
- docs/configuring-playbook-bot-mjolnir.md: move the warning above where the access token is mentioned at first
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
Now that the bot user for Draupnir is created automatically and you no longer need to register it manually since its 2.0.0 version, it does not seem to be sensible to synchronize descriptions about inviting bots between documents for Draupnir and Mjolnir and instruct to invite the bot which does not exist just yet. Inviting the bot user after actually creating it will also spare the possible error message about the nonexistent user.
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
Now that the large table for DNS settings is gone, it is sensible to move the section about DNS setting for server delegation down, below the section for DNS configuration for default services.
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
Based on docs/configuring-playbook-dimension.md and docs/configuring-playbook-bot-go-neb.md
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
- Register a dedicated Matrix user (optional)
- Obtain an access token
Since Dimension has been archived, this is purely for possible use as a template of another component.
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
- Add "To use the bot" if it does not exist: adopt the format of the docs for bridges
- Add "Prerequisites" section if an API key or user account is required
- Use the common instruction for getting an access token
- Replace "Get" with "Obtain" about getting keys or access tokens
- Replace placeholders for access tokens on docs/configuring-playbook-bot-go.neb.md
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
This commit replaces instructions to create passwords, passphrases, or secrets with common ones.
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
The common pattern is "Send `.*?` to the bot (in the room) to see the available commands." If the descripions are about a bot being invited to a certain existing room or room which is not DM, then "in the room" is inserted among them.
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
REUSE is an initiative by FSFE, which intends to make licensing easier with best practices to display legal information through comment headers on source files that can be easily human and machine readable.
Because these files are new and translation shall involve a lot of people as copyright holders, now is the best time to adopt REUSE. As a first implementation, this commit intentionally limits the scope to i18n directory.
Cherry-picked from c737ed0612 and a2445af6d0
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
Usage of matrix_alertmanager_receiver_config_matrix_room_mapping is decribed below in the "Adjusting the playbook configuration" much more nicely.
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
- Replace links to the documentation with ones to projects' README files, if these have been linked to the project directly
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
The original ID (`@example:example.com`) has not matched with the user IDs which those pages explained on "Registering the bot account" section.
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
"To use the bridge, you need to start a chat with …" is well used among the documentation.
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
As using `@alice` and `@bob` on this context is confusing, this commit replaces them with `@email2matrix1` and `@email2matrix2`, respectively.
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
This commit intends to clarify what "short user ID" means by comparing it with ":matrix.example.com"
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
The original ID (`@whatever_you_chose:example.com`) has not matched with the user ID which this page explained above on "Registering the bot user" section.
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
- Use common expressions
- Remove a word puzzle for better l10n experience
- Remove a redundant whitespace character
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
This way, the "installing" sections would cover from beginners to advanced (professional) readers.
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
Also: remove the redundant description about that difference from description about the "just" shortcuts.
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
As the SchildiChat Web docker image was updated with 14a3a01f43 thanks to Aine, the warning is no longer relevant. Note that though the package name says it is a test, it is a test release for SchildiChat Web, and the codebase is Element Web v1.11.86.
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
This is a follow-up to 5483925ee4.
Since any-of-issue/pr-labels overrides any-of-labels, the values specified by the latter need to be specified by the former.
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
Without this option, stale counters for each PR keep restarting whenever any update occurs or a comment is added to them. Since the counters for PR are set to 365 days, ignore-pr-updates should help us to get rid of zombie PRs (which are kept open by bumps).
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
This change makes it possible for terminals to render warning emoji in actual emoji (⚠️), not in text style (⚠).
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
With this commit, actions/stale on GitHub will add a label 'stale' on issues (on spantaleev/matrix-docker-ansible-deploy) after 60 days of inactivity and close the stale issues after 7 days of inactivity. Only issues with labels 'question' and/or 'needs-info' will be processed, and ones with a label 'confirmed' will not be processed automatically.
Please refer https://github.com/marketplace/actions/close-stale-issues
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>