Commit graph

6233 commits

Author SHA1 Message Date
Erick Wibben 2460ab3609
Update Matrix-Registration-Bot main.yml
Line 10, which sets the tag to which docker version to pull was reverted from `v1.1.15` to latest. This gets the playbook working again
2022-06-11 17:58:00 +02:00
Slavi Pantaleev b75735824d
Upgrade certbot (v1.23.0 -> v1.27.0) 2022-06-11 17:58:00 +02:00
GoliathLabs 5b4692fb50
Set version to v1.1.5 2022-06-11 17:57:59 +02:00
GoliathLabs 192b99aaf4
Updated: mautrix-googlechat to v0.3.2 2022-06-11 17:57:59 +02:00
GoliathLabs 55d0552077
Updated: grafana to 8.5.3 2022-06-11 17:57:59 +02:00
GoliathLabs 5afa00fbbf
Updated: etherpad to 1.8.18 2022-06-11 17:57:59 +02:00
GoliathLabs 7ea6b021dd
Updated: ddclient to v3.9.1-ls89 2022-06-11 17:57:59 +02:00
GoliathLabs a8f3c19c67
Reverted URL change 2022-06-11 17:57:59 +02:00
GoliathLabs 0fcc98e76b
Updated: hydrogen to v0.2.29 2022-06-11 17:57:59 +02:00
GoliathLabs 2a1476449b
Updated: hydrogen-web to v0.2.29 2022-06-11 17:57:59 +02:00
GoliathLabs ee060fe2cd
Updated: mautrix-twitter to v0.1.4 2022-06-11 17:57:58 +02:00
GoliathLabs aa8266c048
Updated: mjolnir v1.4.2 2022-06-11 17:57:58 +02:00
Paul B 00a8336134
bridge-whatsapp: add variable to enable end-to-bridge encryption 2022-06-11 17:57:58 +02:00
Paul B 6ea9ed6cb1
bridge-signal: add variable to enable encryption 2022-06-11 17:57:58 +02:00
Slavi Pantaleev a4a612c337
Fix compatibility with ansible=6 / ansible-core=2.13
Details here: https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_6.html#id36

Basically:

```yaml
- name: Prior to 2.13
  debug:
    msg: '[1] + {{ [2] }}'

- name: 2.13 and forward
  debug:
    msg: '{{ [1] + [2] }}'
```

Interestingly, we had been using the new/safe syntax in lofs of places.

We were using the broken one in many others though. Hopefully all
instances were fixed by this patch.
2022-06-11 17:57:58 +02:00
Aine 3bcf31c61e
Update Synapse v1.59.0 -> v.1.59.1 2022-06-11 17:57:58 +02:00
Slavi Pantaleev 28e192b99b
Upgrade hookshot (1.6.1 -> 1.7.0)
This new version should be buildable on arm64.

See: https://github.com/matrix-org/matrix-hookshot/releases/tag/1.7.0

There's still no prebuild arm64 image, so we continue relying on
self-building there.
2022-06-11 17:57:58 +02:00
Aine 0b3e04ba05
Update Postgres (CVE-2022-1552 + last 9.x update)
CVE: https://security-tracker.debian.org/tracker/CVE-2022-1552
Source: https://www.postgresql.org/about/news/postgresql-143-137-1211-1116-and-1021-released-2449/
Postgres 9.6 upgrade (**not a CVE fix, 9.x still vulnerable**): https://www.postgresql.org/docs/release/9.6.24/
2022-06-11 17:57:57 +02:00
Aine 32af01e57e
Update mautrix-whatsapp v0.3.1 -> v0.4.0 2022-06-11 17:57:57 +02:00
Toni Spets be0289e4d3
Upgrade Heisenbridge (1.12.0 -> 1.13.0) 2022-06-11 17:57:57 +02:00
Slavi Pantaleev 29f2bfee8f
Upgrade Synapse (1.58.1 -> 1.59.0) 2022-06-11 17:57:57 +02:00
Slavi Pantaleev 2364b36d25
Work around mx-puppet-discord failing with "No relay found" after reboot
Related to https://gitlab.com/mx-puppet/discord/mx-puppet-discord/-/issues/117

Looks like the bridge is too quick to start and fails to initialize
itself by connecting to Synapse. It's mostly observed after a system
reboot, because Synapse (and everything else) is slower to start.

Once mx-puppet-discord fails to initialize itself, a "No relay found"
error will be observed any time you try to relay a Matrix message to
Discord. Relaying messages in the other direction (Discord to Matrix)
also fails.

With this workaround (longer delay on mx-puppet-discord startup), I
observe mx-puppet-discord working well, even after a full reboot.
Of course, a proper fix is preferable, instead of delaying by a magic
number of seconds.
2022-06-11 17:57:57 +02:00
Slavi Pantaleev 90dffb650c
Upgrade mx-puppet-slack (v0.1.1 -> v0.1.2)
Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1829
2022-06-11 17:57:57 +02:00
Julian-Samuel Gebühr 4d129aab8b
Automatically enable admin api access via nginx (#1830) 2022-06-11 17:57:57 +02:00
Daniel Sonck eff5ebce6c
Change back to working original mx-puppet-slack
Now that v0.1.1 is out, which depends on the functional matrix-slack-parser
it works again.
2022-06-11 17:57:57 +02:00
Aaron Raimist 498906cf5f
Update Element self build repo URL
It forwards to the correct place but might as well just update it to the current URL.
2022-06-11 17:57:56 +02:00
Aaron Raimist f2ef97f1fa
Document git as a potential prereq
Fixes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1792
2022-06-11 17:57:56 +02:00
Aine 319ec33862
Update Cinny v2.0.2 -> v2.0.3 2022-06-11 17:57:56 +02:00
Aine 93e7717c45
Update Cinny v2.0.1 -> v2.0.2 2022-06-11 17:57:56 +02:00
Aine 2782a1ae3d
Update Cinny v2.0.0 -> v2.0.1 2022-06-11 17:57:56 +02:00
Luis b88c9f23e1
Update configuring-playbook-bridge-hookshot.md
fix Hookshot instructions link
2022-06-11 17:57:56 +02:00
brush ac298ae076
Update configuring-well-known.md 2022-06-11 17:57:56 +02:00
brush b60995a954
Update configuring-well-known.md 2022-06-11 17:57:56 +02:00
Didier 'OdyX' Raboud 7557dab315
Bump Slack Appservice to 1.11.0 2022-06-11 17:57:55 +02:00
Aine 7d82b4fc9d
matrix-bot-buscarron - set defaults 2022-06-11 17:57:55 +02:00
Kim Brose b71a4b90d5
Update configuring-playbook-bridge-hookshot.md 2022-06-11 17:57:55 +02:00
Aine b6b5070cde
Update Element 1.10.11 -> 1.10.12 2022-06-11 17:57:55 +02:00
Aine 02fcc2a069
matrix-bot-buscarron v1.1.0 2022-06-11 17:57:55 +02:00
Aine e9713ce2a8
Update cinny v1.8.2 -> v2.0.0 2022-06-11 17:57:55 +02:00
Slavi Pantaleev 3a7ab72b25
Revert "Change back to original mx-puppet-slack"
This reverts commit fcfd00bcb4.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1808

Reverts https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1809

Fixes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1810
2022-06-11 17:57:55 +02:00
Daniel Sonck cc9c8e2747
Change back to original mx-puppet-slack
Closes: #1808
2022-06-11 17:57:55 +02:00
Arkonos a4d33cd316
clarifying where well-known files are created 2022-06-11 17:57:54 +02:00
Arkonos bbb0b0e1ae
clarifying reverse proxying of well-known files 2022-06-11 17:57:54 +02:00
Daniel Sonck 46c27c3efb
Change back to original mx-puppet-discord
Closes: #1801
2022-06-11 17:57:54 +02:00
HarHarLinks b5cbd6aebc
add hookshot feeds support 2022-06-11 17:57:54 +02:00
Kim Brose 8974d591a9
Upgrade Hookshot (1.5.0 -> 1.6.1) 2022-06-11 17:57:54 +02:00
Slavi Pantaleev 71cecd6a55
Do not proxy some endpoints to the generic Synapse worker
These endpoints should not be proxied to a generic Synapse worker
without other preparation (setting up stream writers, sending traffic
to a specific stream writer, etc.).

Disabling them for now. In the future, we'd like to fix up our awk
script to disable them automatically.

This is a fix up for 058fedff91
2022-06-11 17:57:54 +02:00
Paul Tötterman fc105f89a3
typo 2022-06-11 17:57:54 +02:00
Slavi Pantaleev d07883d205
Fix "endpoint seems conditional" determination in workers-doc-to-yaml.awk"
This prevented us from keeping our workers reverse-proxying definitions
updated since Synapse v1.54.0.

The last `workers.md` file we could parse is at commit
02632b3504ad4512c5f5a4f859b3fe326b19c788.
Parsing regressed at commit c56bfb08bc071368db23f3b1c593724eb4f205f0,
because the introduction message for `synapse.app.generic_worker` said
"If":

> If a worker is set up to handle a..

.. which made the AWK script think that definitions below were
conditional (which they're not in this case).

This patch fixes up the regex for determining if a line is conditional
or not, so that it doesn't trip up. Hopefully, it doesn't miss something
important.
2022-06-11 17:57:54 +02:00
Slavi Pantaleev 7df7884041
Upgrade Synapse (1.58.0 -> 1.58.1) 2022-06-11 17:57:53 +02:00