Commit Graph

6637 Commits

Author SHA1 Message Date
6f6dff3e2b Update some Docker images 2019-03-03 12:27:43 +02:00
45618679f5 Reload systemd services when they get updated
Fixes #69 (Github Issue)
2019-03-03 11:55:15 +02:00
041a1947b3 Update Synapse (0.99.1.1 -> 0.99.2) 2019-03-02 10:03:09 +02:00
f2a2cad107 allow exposing mautrix_telegram port 2019-03-01 16:05:01 -07:00
d360c67465 Merge pull request #103 from fretn/master
fixed a small path typo in playbook telemetry docs
2019-03-01 07:27:39 +00:00
6b47ebeaa7 fixed a small path typo in playbook telemetry docs 2019-03-01 07:48:45 +01:00
0b6c28fb23 Mark some Docker images as optional 2019-02-28 14:23:17 +02:00
a43bcd81fe Rename some variables 2019-02-28 11:51:09 +02:00
8cac29a5d5 Update matrix-synapse-rest-auth (0.1.1 -> 0.1.2) 2019-02-28 11:15:26 +02:00
25bdc10617 Follow redirects for some well-known files
The Server spec says that redirects should be followed for
`/.well-known/matrix/server`. So we follow them.

The Client-Server specs doesn't mention redirects, so we don't
follow redirects there.
2019-02-25 21:03:33 +02:00
433780384e Do not use docker_container module
Using `docker_container` with a `cap_drop` argument requires
Ansible >=2.7.

We want to support older versions too (2.4), so we either need to
stop invoking it with `cap_drop` (insecure), or just stop using
the module altogether.

Since it was suffering from other bugs too (not deleting containers
on failure), we've decided to remove `docker_container` usage completely.
2019-02-25 10:42:27 +02:00
639fc0bb5c Treat empty string dig lookup responses as "missing record" 2019-02-22 18:02:10 +02:00
4c512c8e64 Upgrade mxisd (1.3.0 -> 1.3.1) 2019-02-22 15:44:13 +02:00
28bd6dc75b Improve Telegram/Whatsapp instructions 2019-02-22 14:50:07 +02:00
550d398e6c Remove some unnecessary slashes 2019-02-20 21:21:20 +02:00
747574ab56 Update Prerequisites a bit 2019-02-20 11:39:04 +02:00
d552a742f8 Fix Riot caching troubles
Some resources shouldn't be cached right now,
as per https://github.com/vector-im/riot-web/pull/8702

(note all of the suggestions from that pull request were applied,
because some of them do not seem relevant - no such files)

Fixes #98 (Github Issue)
2019-02-16 17:59:41 +02:00
28a5027138 Update changelog a bit 2019-02-16 11:50:06 +02:00
350b25690d Add Riot v1.0 (v1.0.1) support 2019-02-16 11:48:17 +02:00
b79db89221 Improve wording a bit 2019-02-15 10:03:33 +02:00
fcdc2a6c4f Fix incomplete sentence 2019-02-15 10:01:10 +02:00
0f55823c5f Update Synapse (0.99.1 -> 0.99.1.1)
It's not important for us, as it only contains
some ACME-related fix.
2019-02-14 19:43:13 +02:00
1dd4f85e61 Update changelog 2019-02-14 19:05:14 +02:00
eb08e20418 Upgrade Synapse (0.99.0 -> 0.99.1) and sync config
`matrix_synapse_no_tls` is now implicit, so we've gotten rid of it.

The `homeserver.yaml.j2` template has been synchronized with the
configuration generated by Synapse v0.99.1 (some new options
are present, etc.)
2019-02-14 18:40:55 +02:00
df76ae707a Fix inaccurate comment 2019-02-13 14:07:16 +02:00
7a1b5a2024 Update mxisd (1.2.2 -> 1.3.0) 2019-02-10 23:20:05 +02:00
70b2f07fec Add PostgreSQL backup information 2019-02-09 14:36:47 +02:00
42c4de348c Revert "Bind metrics on :: too"
This reverts commit 536c85619f.

Looks like binding metrics on IPv6 (`::`) fails with an error:

socket.gaierror: [Errno -2] Name does not resolve
2019-02-09 13:21:18 +02:00
46accfdb3c Add guide about certificates for other domains
We had something like that on the Server Delegation how-to page,
but it's better if we have it on the SSL certificates page.

Relocated there and improved linking.

Fixes #94 (Github Issue)
2019-02-08 11:59:00 +02:00
f4fa03d4b9 Re-iterate where one can find the well-known files 2019-02-07 19:43:00 +02:00
08635666df Do not attempt to start coturn TLS listeners
We don't provide certificates, so it fails anyway,
but we'd rather suppress the warnings about it too.
2019-02-07 13:20:30 +02:00
f5cd916de8 Update coturn (4.5.0.8 -> 4.5.1.0) 2019-02-07 13:15:59 +02:00
536c85619f Bind metrics on :: too
For consistency with all our other listeners,
we make this one bind on the `::` address too
(both IPv4 and IPv6).

Additional details are in #91 (Github Pull Request).
2019-02-06 14:24:10 +02:00
fd4bd204e1 Improve changelog entry 2019-02-06 14:02:10 +02:00
fca9e8f0b8 Merge pull request #92 from spantaleev/synapse-0.99-prep
Add Synapse v0.99 support
2019-02-06 13:34:24 +02:00
ef903fe544 Add some quick links 2019-02-06 13:30:24 +02:00
e9cfcb8429 Fix another YAML indentation problem on documentation page 2019-02-06 13:04:19 +02:00
92aa5bfa2d Fix YAML indentation on documentation page 2019-02-06 13:03:26 +02:00
33726cdb08 Fix anchor 2019-02-06 13:02:17 +02:00
241a4f9ef9 Add changelog entry for Synapse v0.99 2019-02-06 12:57:33 +02:00
5148f8edf4 Update docs 2019-02-06 09:36:03 +02:00
91a757c581 Add support for reloading Synapse 2019-02-06 09:25:13 +02:00
40f3793af7 Upgrade Synapse to v0.99 and simplify dummy TLS cert logic 2019-02-06 09:17:55 +02:00
5db692f877 Remove some useless homeserver.yaml configuration 2019-02-05 14:02:01 +02:00
772154f3b9 Update Server Delegation docs a bit 2019-02-05 13:38:20 +02:00
738c592c27 Bump Synapse version (0.34.1.1 -> 0.99.0rc4) 2019-02-05 13:33:39 +02:00
119016e858 Cache /.well-known/matrix files for longer 2019-02-05 13:06:17 +02:00
b540427974 Mention alternative ways to do Server Delegation 2019-02-05 13:02:15 +02:00
764a040a90 Make /.well-known/matrix/server optional
People who wish to rely on SRV records can prevent
the `/.well-known/matrix/server` file from being generated
(and thus, served.. which causes trouble).
2019-02-05 12:09:46 +02:00
74710427e5 Allow for the federation port (tcp/8448)'s certificate to be changed
If someone decides to not use `/.well-known/matrix/server` and only
relies on SRV records, then they would need to serve tcp/8448 using
a certificate for the base domain (not for the matrix) domain.

Until now, they could do that by giving the certificate to Synapse
and setting it terminate TLS. That makes swapping certificates
more annoying (Synapse requires a restart to re-read certificates),
so it's better if we can support it via matrix-nginx-proxy.

Mounting certificates (or any other file) into the matrix-nginx-proxy container
can be done with `matrix_nginx_proxy_container_additional_volumes`,
introduced in 96afbbb5a.
2019-02-05 12:09:46 +02:00