Преглед изворни кода

Merge branch 'spantaleev:master' into synapse-s3-support

pull/1769/head
Markus пре 3 година
committed by GitHub
родитељ
комит
a488fc2de9
No known key found for this signature in database GPG Key ID: 4AEE18F83AFDEB23
12 измењених фајлова са 67 додато и 2 уклоњено
  1. +28
    -0
      CHANGELOG.md
  2. +3
    -0
      docs/configuring-playbook-backup-borg.md
  3. +3
    -0
      docs/configuring-playbook-postgres-backup.md
  4. +7
    -0
      docs/configuring-playbook.md
  5. +1
    -1
      roles/matrix-backup-borg/tasks/init.yml
  6. +4
    -0
      roles/matrix-base/defaults/main.yml
  7. +4
    -0
      roles/matrix-grafana/tasks/setup.yml
  8. +4
    -0
      roles/matrix-prometheus/tasks/setup_install.yml
  9. +1
    -1
      roles/matrix-synapse/defaults/main.yml
  10. +4
    -0
      roles/matrix-synapse/tasks/ext/encryption-disabler/setup_install.yml
  11. +4
    -0
      roles/matrix-synapse/tasks/ext/rest-auth/setup_install.yml
  12. +4
    -0
      roles/matrix-synapse/tasks/ext/shared-secret-auth/setup_install.yml

+ 28
- 0
CHANGELOG.md Прегледај датотеку

@@ -1,3 +1,31 @@
# 2022-04-19

## Borg backup support

Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now set up [Borg](https://www.borgbackup.org/) backups with [borgmatic](https://torsion.org/borgmatic/) of your Matrix server.

See our [Setting up borg backup](docs/configuring-playbook-backup-borg.md) documentation to get started.


## (Compatibility Break) Upgrading to Synapse v1.57 on setups using workers may require manual action

If you're running a worker setup for Synapse (`matrix_synapse_workers_enabled: true`), the [Synapse v1.57 upgrade notes](https://github.com/matrix-org/synapse/blob/v1.57.0rc1/docs/upgrade.md#changes-to-database-schema-for-application-services) say that you may need to take special care when upgrading:

> Synapse v1.57.0 includes a change to the way transaction IDs are managed for application services. If your deployment uses a dedicated worker for application service traffic, **it must be stopped** when the database is upgraded (which normally happens when the main process is upgraded), to ensure the change is made safely without any risk of reusing transaction IDs.

If you're not running an `appservice` worker (`matrix_synapse_workers_preset: little-federation-helper` or `matrix_synapse_workers_appservice_workers_count: 0`), you are probably safe to upgrade as per normal, without taking any special care.

If you are running a setup with an `appservice` worker, or otherwise want to be on the safe side, we recommend the following upgrade path:

0. Pull the latest playbook changes
1. Stop all services (`ansible-playbook -i inventory/hosts setup.yml --tags=stop`)
2. Re-run the playbook (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-all`)
3. Start Postgres (`systemctl start matrix-postgres` on the server)
4. Start the main Synapse process (`systemctl start matrix-synapse` on the server)
5. Wait a while so that Synapse can start and complete the database migrations. You can use `journalctl -fu matrix-synapse` on the server to get a clue. Waiting a few minutes should also be enough.
6. It should now be safe to start all other services. `ansible-playbook -i inventory/hosts setup.yml --tags=start` will do it for you


# 2022-04-14

## (Compatibility Break) Changes to `docker-src` permissions necessitating manual action


+ 3
- 0
docs/configuring-playbook-backup-borg.md Прегледај датотеку

@@ -8,6 +8,9 @@ You will need a remote server where borg will store the backups. There are hoste

The backup will run based on `matrix_backup_borg_schedule` var (systemd timer calendar), default: 4am every day.

By default, if you're using the integrated Postgres database server (as opposed to [an external Postgres server](configuring-playbook-external-postgres.md)), Borg backups will also include dumps of your Postgres database. An alternative solution for backing up the Postgres database is [postgres backup](configuring-playbook-postgres-backup.md). If you decide to go with another solution, you can disable Postgres-backup support for Borg using the `matrix_backup_borg_postgresql_enabled` variable.


## Prerequisites

1. Create a new SSH key:


+ 3
- 0
docs/configuring-playbook-postgres-backup.md Прегледај датотеку

@@ -2,6 +2,9 @@

The playbook can install and configure [docker-postgres-backup-local](https://github.com/prodrigestivill/docker-postgres-backup-local) for you.

For a more complete backup solution (one that includes not only Postgres, but also other configuration/data files), you may wish to look into [borg backup](configuring-playbook-backup-borg.md) instead.


## Adjusting the playbook configuration

Minimal working configuration (`inventory/host_vars/matrix.DOMAIN/vars.yml`) to enable Postgres backup:


+ 7
- 0
docs/configuring-playbook.md Прегледај датотеку

@@ -152,6 +152,13 @@ When you're done with all the configuration you'd like to do, continue with [Ins
- [Setting up Mjolnir](configuring-playbook-bot-mjolnir.md) - a moderation tool/bot (optional)


### Backups

- [Setting up borg backup](configuring-playbook-backup-borg.md) - a full Matrix server backup solution, including the Postgres database (optional)

- [Setting up postgres backup](configuring-playbook-postgres-backup.md) - a Postgres-database backup solution (note: does not include other files) (optional)


### Other specialized services

- [Setting up the Sygnal push gateway](configuring-playbook-sygnal.md) (optional)

+ 1
- 1
roles/matrix-backup-borg/tasks/init.yml Прегледај датотеку

@@ -1,4 +1,4 @@
---
- set_fact:
matrix_systemd_services_list: "{{ matrix_systemd_services_list + ['matrix-backup-borg.service', 'matrix-backup-borg.timer'] }}"
matrix_systemd_services_list: "{{ matrix_systemd_services_list + ['matrix-backup-borg.timer'] }}"
when: matrix_backup_borg_enabled|bool

+ 4
- 0
roles/matrix-base/defaults/main.yml Прегледај датотеку

@@ -71,6 +71,10 @@ matrix_container_global_registry_prefix: "docker.io/"
matrix_container_retries_count: 10
matrix_container_retries_delay: 10

# Each get_url will retry on failed attempt 10 times with delay of 10 seconds between each attempt.
matrix_geturl_retries_count: 10
matrix_geturl_retries_delay: 10

matrix_user_username: "matrix"
matrix_user_groupname: "matrix"



+ 4
- 0
roles/matrix-grafana/tasks/setup.yml Прегледај датотеку

@@ -70,6 +70,10 @@
group: "{{ matrix_user_groupname }}"
with_items: "{{ matrix_grafana_dashboard_download_urls_all }}"
when: matrix_grafana_enabled|bool
register: result
retries: "{{ matrix_geturl_retries_count }}"
delay: "{{ matrix_geturl_retries_delay }}"
until: result is not failed

- name: Ensure matrix-grafana.service installed
template:


+ 4
- 0
roles/matrix-prometheus/tasks/setup_install.yml Прегледај датотеку

@@ -32,6 +32,10 @@
owner: "{{ matrix_user_username }}"
group: "{{ matrix_user_groupname }}"
when: "matrix_prometheus_scraper_synapse_rules_enabled|bool"
register: result
retries: "{{ matrix_geturl_retries_count }}"
delay: "{{ matrix_geturl_retries_delay }}"
until: result is not failed

- name: Ensure prometheus.yml installed
copy:


+ 1
- 1
roles/matrix-synapse/defaults/main.yml Прегледај датотеку

@@ -9,7 +9,7 @@ matrix_synapse_container_image_self_build_repo: "https://github.com/matrix-org/s

matrix_synapse_docker_image: "{{ matrix_synapse_docker_image_name_prefix }}matrixdotorg/synapse:{{ matrix_synapse_docker_image_tag }}"
matrix_synapse_docker_image_name_prefix: "{{ 'localhost/' if matrix_synapse_container_image_self_build else matrix_container_global_registry_prefix }}"
matrix_synapse_version: v1.57.0
matrix_synapse_version: v1.57.1
matrix_synapse_docker_image_tag: "{{ matrix_synapse_version }}"
matrix_synapse_docker_image_force_pull: "{{ matrix_synapse_docker_image.endswith(':latest') }}"



+ 4
- 0
roles/matrix-synapse/tasks/ext/encryption-disabler/setup_install.yml Прегледај датотеку

@@ -8,6 +8,10 @@
mode: 0440
owner: "{{ matrix_user_username }}"
group: "{{ matrix_user_groupname }}"
register: result
retries: "{{ matrix_geturl_retries_count }}"
delay: "{{ matrix_geturl_retries_delay }}"
until: result is not failed

- set_fact:
matrix_synapse_modules: |


+ 4
- 0
roles/matrix-synapse/tasks/ext/rest-auth/setup_install.yml Прегледај датотеку

@@ -13,6 +13,10 @@
mode: 0440
owner: "{{ matrix_user_username }}"
group: "{{ matrix_user_groupname }}"
register: result
retries: "{{ matrix_geturl_retries_count }}"
delay: "{{ matrix_geturl_retries_delay }}"
until: result is not failed

- set_fact:
matrix_synapse_password_providers_enabled: true


+ 4
- 0
roles/matrix-synapse/tasks/ext/shared-secret-auth/setup_install.yml Прегледај датотеку

@@ -18,6 +18,10 @@
mode: 0440
owner: "{{ matrix_user_username }}"
group: "{{ matrix_user_groupname }}"
register: result
retries: "{{ matrix_geturl_retries_count }}"
delay: "{{ matrix_geturl_retries_delay }}"
until: result is not failed

- set_fact:
matrix_synapse_modules: |


Loading…
Откажи
Сачувај