mirror of
https://github.com/spantaleev/matrix-docker-ansible-deploy.git
synced 2025-02-06 07:15:13 +01:00
Compare commits
No commits in common. "d949d4d1fab7f1357a9e7f0fb236c2bd3171eae4" and "6e66f8aaa21b5cfd5c16c6dcf302319b143ba0c3" have entirely different histories.
d949d4d1fa
...
6e66f8aaa2
@ -10,16 +10,16 @@ In the sample `vars.yml` ([`examples/vars.yml`](../examples/vars.yml)), we recom
|
|||||||
|
|
||||||
To use such an identifier, you don't need to install anything on the actual `example.com` server. Instead, you need to instruct the Matrix network that Matrix services for `example.com` are redirected over to `matrix.example.com`. This redirection is also known as "delegation".
|
To use such an identifier, you don't need to install anything on the actual `example.com` server. Instead, you need to instruct the Matrix network that Matrix services for `example.com` are redirected over to `matrix.example.com`. This redirection is also known as "delegation".
|
||||||
|
|
||||||
As we discuss in [Server Delegation](howto-server-delegation.md), server delegation can be configured in either of these ways:
|
As we discuss in [Server Delegation](howto-server-delegation.md), server delegation can be configured in either way:
|
||||||
|
|
||||||
- Setting up a `/.well-known/matrix/server` file on the base domain (`example.com`)
|
- Setting up a `/.well-known/matrix/server` file on the base domain (`example.com`)
|
||||||
- Setting up a `_matrix._tcp` DNS SRV record
|
- Setting up a `_matrix._tcp` DNS SRV record
|
||||||
|
|
||||||
For simplicity reasons, this playbook recommends you to set up server delegation via a `/.well-known/matrix/server` file, instead of using a DNS SRV record.
|
For simplicity reasons, this playbook recommends you to set up server delegation via a `/.well-known/matrix/server` file, instead of using a DNS SRV record.
|
||||||
|
|
||||||
If you choose the recommended method (file-based delegation), you do not need to configure the DNS record to enable server delegation. You will need to add a necessary configuration later, when you [finalize the installation](installing.md#finalize-the-installation) after installing and starting Matrix services.
|
If you choose the recommended method, you do not need to configure the DNS record to enable server delegation. You will need to add a necessary configuration later, when you [finalize the installation](installing.md#finalize-the-installation) after installing and starting Matrix services.
|
||||||
|
|
||||||
On the other hand, if you choose this method (setting up a DNS SRV record), you need to configure the additional DNS record as well as adjust SSL certificate handling. Take a look at this documentation for more information: [Server Delegation via a DNS SRV record (advanced)](howto-server-delegation.md#server-delegation-via-a-dns-srv-record-advanced)
|
On the other hand, if you choose the other method (setting the DNS SRV record), you need to configure the additional DNS record. Take a look at this documentation for more information: [Server Delegation via a DNS SRV record (advanced)](howto-server-delegation.md#server-delegation-via-a-dns-srv-record-advanced)
|
||||||
|
|
||||||
## DNS settings for services enabled by default
|
## DNS settings for services enabled by default
|
||||||
|
|
||||||
|
@ -1,8 +1,8 @@
|
|||||||
# Serving the base domain (optional)
|
# Serving the base domain (optional)
|
||||||
|
|
||||||
By default, this playbook sets up services on your Matrix server (`matrix.example.com`), but has it configured so that it presents itself as the base domain (`example.com`). To have this server officially be responsible for Matrix services for the base domain (`example.com`), you need to set up server delegation / redirection.
|
By default, this playbook sets up services on your Matrix server (`matrix.example.com`). To have this server officially be responsible for Matrix services for the base domain (`example.com`), you need to set up server delegation / redirection.
|
||||||
|
|
||||||
As we discuss in [Server Delegation](howto-server-delegation.md), server delegation / redirection can be configured in either of these ways:
|
As we discuss in [Server Delegation](howto-server-delegation.md), server delegation / redirection can be configured in either way:
|
||||||
|
|
||||||
- Setting up a `/.well-known/matrix/server` file on the base domain (`example.com`)
|
- Setting up a `/.well-known/matrix/server` file on the base domain (`example.com`)
|
||||||
- Setting up a `_matrix._tcp` DNS SRV record
|
- Setting up a `_matrix._tcp` DNS SRV record
|
||||||
|
@ -2,7 +2,7 @@
|
|||||||
|
|
||||||
By default, this playbook sets up services on your Matrix server (`matrix.example.com`). To have this server officially be responsible for Matrix services for the base domain (`example.com`), you need to set up server delegation / redirection.
|
By default, this playbook sets up services on your Matrix server (`matrix.example.com`). To have this server officially be responsible for Matrix services for the base domain (`example.com`), you need to set up server delegation / redirection.
|
||||||
|
|
||||||
Server delegation can be configured in either of these ways:
|
Server delegation can be configured in either way:
|
||||||
|
|
||||||
- [Setting up a `/.well-known/matrix/server` file](#server-delegation-via-a-well-known-file) on the base domain (`example.com`)
|
- [Setting up a `/.well-known/matrix/server` file](#server-delegation-via-a-well-known-file) on the base domain (`example.com`)
|
||||||
- [Setting up a `_matrix._tcp` DNS SRV record](#server-delegation-via-a-dns-srv-record-advanced)
|
- [Setting up a `_matrix._tcp` DNS SRV record](#server-delegation-via-a-dns-srv-record-advanced)
|
||||||
@ -36,7 +36,7 @@ Otherwise, you can decide to go against the default for this playbook, and inste
|
|||||||
|
|
||||||
## Server Delegation via a DNS SRV record (advanced)
|
## Server Delegation via a DNS SRV record (advanced)
|
||||||
|
|
||||||
**Note**: doing Server Delegation via a DNS SRV record is a more **advanced** way to do it and is not the default for this playbook. This is usually **much more complicated** to set up, so **we don't recommend it**. If you're not an experienced sysadmin, you'd better stay away from this.
|
**Note**: doing Server Delegation via a DNS SRV record is a more **advanced** way to do it and is not the default for this playbook. This is usually **much more complicated** to set up, so **we don't recommend it**. If you're not an experience sysadmin, you'd better stay away from this.
|
||||||
|
|
||||||
As per the [Server-Server spec](https://matrix.org/docs/spec/server_server/r0.1.0.html#server-discovery), it's possible to do Server Delegation using only a SRV record (without a `/.well-known/matrix/server` file).
|
As per the [Server-Server spec](https://matrix.org/docs/spec/server_server/r0.1.0.html#server-discovery), it's possible to do Server Delegation using only a SRV record (without a `/.well-known/matrix/server` file).
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user