matrix-docker-ansible-deploy/CHANGELOG.md

# 2018-08-17

## Disabling some unnecessary Synapse services

The following services are not necessary, so they have been disabled:
- on the federation port (8448): the `client` service
- on the http port (80): the old Angular `webclient` and the `federation` service

Federation runs only on the federation port (8448) now.
The Client APIs run only on the http port (80) now.


# 2018-08-15

## mxisd Identity Server support

The playbook now sets up an [mxisd](https://github.com/kamax-io/mxisd) Identity Server for you by default.
Additional details are available in [Adjusting mxisd Identity Server configuration](docs/configuring-playbook-mxisd.md).


# 2018-08-14

## Email-sending support

The playbook now configures an email-sending service (postfix) by default.
Additional details are available in [Adjusting email-sending settings](docs/configuring-playbook-email.md).

With this, Matrix Synapse is able to send email notifications for missed messages, etc.


# 2018-08-08


## (BC Break) Renaming playbook variables

The following playbook variables were renamed:

- from `matrix_max_upload_size_mb` to `matrix_synapse_max_upload_size_mb`
- from `matrix_max_log_file_size_mb` to `matrix_synapse_max_log_file_size_mb`
- from `matrix_max_log_files_count` to `matrix_synapse_max_log_files_count`
- from `docker_matrix_image` to `matrix_docker_image_synapse`
- from `docker_nginx_image` to `matrix_docker_image_nginx`
- from `docker_riot_image` to `matrix_docker_image_riot`
- from `docker_goofys_image` to `matrix_docker_image_goofys`
- from `docker_coturn_image` to `matrix_docker_image_coturn`

If you're overriding any of them in your `vars.yml` file, you'd need to change to the new names.


## Renaming Ansible playbook tag

The command for executing the whole playbook has changed.
The `setup-main` tag got renamed to `setup-all`.


## Docker container linking

Changed the way the Docker containers are linked together. The ones that need to communicate with others operate in a `matrix` network now and not in the default bridge network.
Only run federation on 8448 and client on 80 This disables federation on the 80 port, as it's not necessary. We also disable the old Angular webclient. For the federation port (8448), we disable the client APIs as those are not necessary. Those can even cause trouble if one doesn't know about them and thinks that guarding the client APIs at the 80 port is enough. 2018-08-17 04:27:02 +00:00			`# 2018-08-17`

			`## Disabling some unnecessary Synapse services`

			`The following services are not necessary, so they have been disabled:`
			- on the federation port (8448): the `client` service
			- on the http port (80): the old Angular `webclient` and the `federation` service

			`Federation runs only on the federation port (8448) now.`
			`The Client APIs run only on the http port (80) now.`


Add mxisd Identity Server support 2018-08-15 07:23:22 +00:00			`# 2018-08-15`

			`## mxisd Identity Server support`

			`The playbook now sets up an [mxisd](https://github.com/kamax-io/mxisd) Identity Server for you by default.`
			`Additional details are available in [Adjusting mxisd Identity Server configuration](docs/configuring-playbook-mxisd.md).`


Add email-sending support 2018-08-14 11:11:41 +00:00			`# 2018-08-14`

			`## Email-sending support`

			`The playbook now configures an email-sending service (postfix) by default.`
			`Additional details are available in [Adjusting email-sending settings](docs/configuring-playbook-email.md).`

			`With this, Matrix Synapse is able to send email notifications for missed messages, etc.`


Put all containers in their own isolated Docker network (matrix) Moving away from using the default bridge network to using our own. This isolates our services from other Docker containers running on the default network on the same host. The benefits are that: - isolation is a little better - we no longer share a default bridge network with any other containers that might be running on the host - there are no longer hard dependencies - we do service discovery by DNS name, and not via explicit `--link` usage during container start, so containers can start out of order and fail without bringing down others with them (`matrix-nginx-proxy` can continue running, even if one of the other services dies) In the future, when other services get introduced, the increased resilience and simplicity will help as well. 2018-08-08 05:23:36 +00:00			`# 2018-08-08`


Rename a bunch of playbook variables for better consistency 2018-08-08 06:17:18 +00:00			`## (BC Break) Renaming playbook variables`

			`The following playbook variables were renamed:`

			- from `matrix_max_upload_size_mb` to `matrix_synapse_max_upload_size_mb`
			- from `matrix_max_log_file_size_mb` to `matrix_synapse_max_log_file_size_mb`
			- from `matrix_max_log_files_count` to `matrix_synapse_max_log_files_count`
			- from `docker_matrix_image` to `matrix_docker_image_synapse`
			- from `docker_nginx_image` to `matrix_docker_image_nginx`
			- from `docker_riot_image` to `matrix_docker_image_riot`
			- from `docker_goofys_image` to `matrix_docker_image_goofys`
			- from `docker_coturn_image` to `matrix_docker_image_coturn`

			If you're overriding any of them in your `vars.yml` file, you'd need to change to the new names.


Rename Ansible playbook tag (setup-main -> setup-all) 2018-08-08 06:03:37 +00:00			`## Renaming Ansible playbook tag`

			`The command for executing the whole playbook has changed.`
			The `setup-main` tag got renamed to `setup-all`.


Put all containers in their own isolated Docker network (matrix) Moving away from using the default bridge network to using our own. This isolates our services from other Docker containers running on the default network on the same host. The benefits are that: - isolation is a little better - we no longer share a default bridge network with any other containers that might be running on the host - there are no longer hard dependencies - we do service discovery by DNS name, and not via explicit `--link` usage during container start, so containers can start out of order and fail without bringing down others with them (`matrix-nginx-proxy` can continue running, even if one of the other services dies) In the future, when other services get introduced, the increased resilience and simplicity will help as well. 2018-08-08 05:23:36 +00:00			`## Docker container linking`

			Changed the way the Docker containers are linked together. The ones that need to communicate with others operate in a `matrix` network now and not in the default bridge network.