Solved matrix bugs

This commit is contained in:
Kevin Veen-Birkenbach 2024-01-20 12:46:07 +01:00
parent 722c017088
commit ea32b08a7b
6 changed files with 32 additions and 27 deletions

View File

@ -2,11 +2,11 @@
# It is necessary to shut the projects down, when reset is activated.
# Otherwise it can lead to this bug:
# https://github.com/ansible/ansible/issues/10244
- name: shut down docker compose project
command:
cmd: docker-compose -p "{{docker_compose_project_name}}" down
listen: docker compose project setup
when: mode_reset | bool
#- name: shut down docker compose project
# command:
# cmd: docker-compose -p "{{docker_compose_project_name}}" down
# listen: docker compose project setup
# when: mode_reset | bool
- name: docker compose project setup
command:

View File

@ -43,6 +43,19 @@ for db in matrix mautrix_whatsapp_bridge mautrix_telegram_bridge mautrix_signal_
docker compose down -v
```
## Bridges
### General
Contact one of the following bots for more information:
- @signalbot:yourdomain.tld
- @telegrambot:yourdomain.tld
- @whatsappbot:yourdomain.tld
- @slackbot:yourdomain.tld
### Slack
For login with Token checkout [this guide](https://docs.mau.fi/bridges/go/slack/authentication.html).
## Debug:
- https://federationtester.matrix.org/

View File

@ -96,8 +96,17 @@
dest: "{{docker_compose_instance_directory}}docker-compose.yml"
notify: docker compose project setup
- name: flush docker service
meta: flush_handlers
- name: docker compose project setup
command:
cmd: docker-compose -p "{{docker_compose_project_name}}" up -d --force-recreate
chdir: "{{docker_compose_instance_directory}}"
environment:
COMPOSE_HTTP_TIMEOUT: 600
DOCKER_CLIENT_TIMEOUT: 600
register: result
until: result is succeeded
retries: 12
delay: 30
- name: wait for registration files
wait_for:

View File

@ -30,9 +30,7 @@ services:
{% include 'templates/docker/container/depends-on-also-database.yml.j2' %}
{% for item in bridges %}
mautrix-{{item.bridge_name}}:
# The condition service_healthy does not work.
# In practice is does not make a difference anyhow, due to the reason that synapse will restart until it is running
condition: service_started
condition: service_healthy
{% endfor %}
{% include 'templates/docker/container/networks.yml.j2' %}

View File

@ -10,20 +10,5 @@ server {
{% include 'roles/nginx-matomo-tracking/templates/matomo-tracking.conf.j2' %}
{% endif %}
location ~ ^(/_matrix|/_synapse/client) {
# note: do not add a path (even a single /) after the port in `proxy_pass`,
# otherwise nginx will canonicalise the URI and cause signature verification
# errors.
proxy_pass http://127.0.0.1:{{http_port}};
proxy_set_header X-Forwarded-For $remote_addr;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header Host $host;
# Nginx by default only allows file uploads up to 1M in size
# Increase client_max_body_size to match max_upload_size defined in homeserver.yaml
client_max_body_size 50M;
# Synapse responses may be chunked, which is an HTTP/1.1 feature.
proxy_http_version 1.1;
}
{% include 'roles/nginx-docker-reverse-proxy/templates/proxy_pass.conf.j2' %}
}

View File

@ -18,7 +18,7 @@ database:
cp_min: 5
cp_max: 10
log_config: "/data/{{domain_matrix_synapse}}.log.config"
media_store_path: /data/media_store
media_store_path: "/data/media_store"
registration_shared_secret: "{{matrix_registration_shared_secret}}"
report_stats: true
macaroon_secret_key: "{{matrix_macaroon_secret_key}}"