Matrix Docker Ansible eploy

Histórico

Slavi Pantaleev 0500127456 Fix the sqlite database URI for the mautrix-meta bridges Both roles derived `..._appservice_database_uri` as `'sqlite:///' + <path>`. mautrix-go hands that string to go-sqlite3 as a filename rather than parsing it as a URL, so the bridge cannot open its database and dies at startup: FTL Failed to initialize database error="... unable to open database file: no such file or directory" Every other mautrix bridge role here passes the bare in-container path. This has stayed hidden because group_vars/matrix_servers selects postgres whenever postgres is enabled, which is the default - so almost nobody reaches the sqlite branch. Anyone who does gets a bridge that never starts. Found by the mautrix-meta-messenger Molecule scenario, which runs sqlite deliberately. The scenario's override is dropped and its assertion now compares the rendered URI against the path the role defines, so the derived value is what is under test rather than the scenario's own. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SEH3vxYSQ5SV4N5z61eyGT		hace 4 días
..
defaults	Fix the sqlite database URI for the mautrix-meta bridges	hace 4 días
tasks	Decouple mautrix-meta-instagram from mautrix-meta-messenger and fix Instagram self-building	hace 2 semanas
templates	Decouple mautrix-meta-instagram from mautrix-meta-messenger and fix Instagram self-building	hace 2 semanas
README.md	Decouple mautrix-meta-instagram from mautrix-meta-messenger and fix Instagram self-building	hace 2 semanas

README.md

matrix-mautrix-meta-instagram

This role installs the Instagram bridge developed in the mautrix-meta repository.

This role used to be auto-generated from the matrix-bridge-mautrix-meta-messenger role, back when a single mautrix-meta binary served both Messenger and Instagram depending on a mode configuration setting. Since mautrix-meta v26.07, Instagram is a separate binary with its own container image (ig- prefixed tags) and its own configuration schema, so the two roles are maintained independently.