mirror of
https://github.com/spantaleev/matrix-docker-ansible-deploy.git
synced 2026-04-25 09:57:35 +00:00
5b7a1c2a6c
Matches the earlier Python -> Go rewrites of the other mautrix-* bridges. Related to: - https://github.com/mautrix/telegram/releases/tag/v0.2604.0 - https://mau.fi/blog/2026-04-mautrix-release/ The bridge is now a Go binary with upstream-handled automatic database and config migration on first start, so in-place upgrades on Postgres should Just Work for users on the defaults. The lottieconverter sidecar container is gone (bundled upstream), and the public web-based login endpoint is gone (login happens inside Matrix now). Upstream v0.2604.0 has a known bug in the legacy SQLite migration that can corrupt data. The role detects legacy Python-bridge SQLite databases (via the `telethon_sessions` table signature) and refuses to upgrade, pointing users to switch to Postgres (playbook-managed pgloader migration) or wait for the next upstream release. The guard is isolated in its own `validate_config_sqlite_legacy_migration_bug.yml` so it can be deleted cleanly once upstream fixes the bug. Removed variables (all caught by the deprecation check in `validate_config.yml` with actionable rename/removal hints): the entire `_hostname` / `_path_prefix` / `_scheme` / `_public_endpoint` / `_appservice_public_*` / `_container_labels_public_endpoint_*` / `_container_http_host_bind_port` family (web login endpoint is gone); `_bot_token` (old-style relaybot is gone, use the common bridgev2 relay mode); `_filter_mode` (dropped upstream); `_bridge_login_shared_secret_map*` (use Appservice Double Puppet); `_username_template`, `_alias_template`, `_displayname_template` (templates moved under `network:`, new Go-template syntax, exposed via `_network_displayname_template`); all `_lottieconverter_*` variables; `_appservice_database` (renamed to `_appservice_database_uri`). Added playbook-time validation that catches legacy permission values (`relaybot`, `puppeting`, `full`) in the fully-merged config (so overrides via `matrix_mautrix_telegram_configuration_extension_yaml` are caught too), with a mapping hint in the error message. Other notes: - The legacy sqlite->postgres relocation of `{base_path}/mautrix-telegram.db` to `{data_path}/mautrix-telegram.db` now happens BEFORE the pgloader migration step, so users who flip to Postgres as part of this upgrade get their data imported correctly. - The Ketesa managed-user regex for the telegram namespace is updated to match both regular IDs and the new `channel-<id>` form used by bridgev2. - `matrix_playbook_migration_expected_version` bumped to v2026.04.24.0, with a new breaking-change entry pointing at the CHANGELOG section. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
68 lines
3.4 KiB
YAML
68 lines
3.4 KiB
YAML
---
|
|
# This variable acknowledges that you've reviewed breaking changes up to this version.
|
|
# The playbook will fail if this is outdated, guiding you through what changed.
|
|
# See the changelog: https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/CHANGELOG.md
|
|
matrix_playbook_migration_validated_version: v2026.04.24.0
|
|
|
|
# The bare domain name which represents your Matrix identity.
|
|
# Matrix user IDs for your server will be of the form (`@alice:example.com`).
|
|
#
|
|
# Note: this playbook does not touch the server referenced here.
|
|
# Installation happens on another server ("matrix.example.com", see `matrix_server_fqn_matrix`).
|
|
#
|
|
# If you've deployed using the wrong domain, you'll have to run the Uninstalling step,
|
|
# because you can't change the Domain after deployment.
|
|
matrix_domain: example.com
|
|
|
|
# The Matrix homeserver software to install.
|
|
# See:
|
|
# - `roles/custom/matrix-base/defaults/main.yml` for valid options
|
|
# - the `docs/configuring-playbook-IMPLEMENTATION_NAME.md` documentation page, if one is available for your implementation choice
|
|
#
|
|
# By default, we use Synapse, because it's the only full-featured Matrix server at the moment.
|
|
#
|
|
# Note that the homeserver implementation of a server will not be able to be changed without data loss.
|
|
matrix_homeserver_implementation: synapse
|
|
|
|
# A secret used as a base, for generating various other secrets.
|
|
# You can put any string here, but generating a strong one is preferred. You can create one with a command like `pwgen -s 64 1`.
|
|
matrix_homeserver_generic_secret_key: ''
|
|
|
|
# By default, the playbook manages its own Traefik (https://doc.traefik.io/traefik/) reverse-proxy server.
|
|
# It will retrieve SSL certificates for you on-demand and forward requests to all other components.
|
|
# For alternatives, see `docs/configuring-playbook-own-webserver.md`.
|
|
matrix_playbook_reverse_proxy_type: playbook-managed-traefik
|
|
|
|
# Controls whether container networks will be created with IPv6 support.
|
|
#
|
|
# If you also have IPv6 support on your server/network and AAAA DNS records pointing to the server,
|
|
# enabling this will effectively give you full public IPv6 connectivity (powered by NAT66).
|
|
#
|
|
# We recommend leaving this enabled even if you don't currently have IPv6 connectivity on your server/network.
|
|
# This way, once you eventually get IPv6 connectivity, you won't have to change anything (besides DNS records).
|
|
#
|
|
# Flipping this setting later on requires manual work (stopping services, deleting and recreating all container networks).
|
|
#
|
|
# In the future, this setting will likely default to `true`, so if you really want IPv6 disabled, explicitly set this to `false`.
|
|
#
|
|
# People managing Docker themselves and running an older Docker version will need additional configuration.
|
|
#
|
|
# Learn more in `docs/configuring-ipv6.md`.
|
|
devture_systemd_docker_base_ipv6_enabled: true
|
|
|
|
# A Postgres password to use for the superuser Postgres user (called `matrix` by default).
|
|
#
|
|
# The playbook creates additional Postgres users and databases (one for each enabled service) using this superuser account.
|
|
#
|
|
# Changing this value subsequently requires manual work.
|
|
# The value used here must be shorter than 100 characters.
|
|
postgres_connection_password: ''
|
|
|
|
# You can limit heavy room joins on constrained hosts.
|
|
# See:
|
|
# docs/configuring-playbook-synapse.md#limit-joining-heavy-rooms-on-constrained-hosts
|
|
#
|
|
# matrix_synapse_limit_remote_rooms_enabled: true
|
|
# matrix_synapse_limit_remote_rooms_complexity: 1.0
|
|
# matrix_synapse_limit_remote_rooms_admins_can_join: false
|