mirror of
https://github.com/spantaleev/matrix-docker-ansible-deploy.git
synced 2024-12-22 04:34:00 +00:00
Update README and changelog
This commit is contained in:
parent
fc7ba153b1
commit
a21b410c51
22
CHANGELOG.md
22
CHANGELOG.md
@ -1,3 +1,25 @@
|
|||||||
|
# 2019-05-21
|
||||||
|
|
||||||
|
## Synapse no longer required
|
||||||
|
|
||||||
|
The playbook no longer insists on installing [Synapse](https://github.com/matrix-org/synapse) via the `matrix-synapse` role.
|
||||||
|
|
||||||
|
If you would prefer to install Synapse another way and just use the playbook to install other services, it should be possible (`matrix_synapse_enabled: false`).
|
||||||
|
|
||||||
|
Note that it won't necessarily be the best experience, since the playbook wires things to Synapse by default.
|
||||||
|
If you're using your own Synapse instance (especially one not running in a container), you may have to override many variables to point them to the correct place.
|
||||||
|
|
||||||
|
Having Synapse not be a required component potentially opens the door for installing alternative Matrix homeservers.
|
||||||
|
|
||||||
|
|
||||||
|
## Bridges are now separate from the Synapse role
|
||||||
|
|
||||||
|
Bridges are no longer part of the `matrix-synapse` role.
|
||||||
|
Each bridge now lives in its own separate role (`roles/matrix-bridge-*`).
|
||||||
|
|
||||||
|
These bridge roles are independent of the `matrix-synapse` role, so it should be possible to use them with a Synapse instance installed another way (not through the playbook).
|
||||||
|
|
||||||
|
|
||||||
# 2019-05-09
|
# 2019-05-09
|
||||||
|
|
||||||
Besides a myriad of bug fixes and minor improvements, here are the more notable (bigger) features we can announce today.
|
Besides a myriad of bug fixes and minor improvements, here are the more notable (bigger) features we can announce today.
|
||||||
|
@ -8,7 +8,7 @@ That is, it lets you join the Matrix network with your own `@<username>:<your-do
|
|||||||
|
|
||||||
Using this playbook, you can get the following services configured on your server:
|
Using this playbook, you can get the following services configured on your server:
|
||||||
|
|
||||||
- a [Synapse](https://github.com/matrix-org/synapse) homeserver - storing your data and managing your presence in the [Matrix](http://matrix.org/) network
|
- (optional, default) a [Synapse](https://github.com/matrix-org/synapse) homeserver - storing your data and managing your presence in the [Matrix](http://matrix.org/) network
|
||||||
|
|
||||||
- (optional) [Amazon S3](https://aws.amazon.com/s3/) storage for Synapse's content repository (`media_store`) files using [Goofys](https://github.com/kahing/goofys)
|
- (optional) [Amazon S3](https://aws.amazon.com/s3/) storage for Synapse's content repository (`media_store`) files using [Goofys](https://github.com/kahing/goofys)
|
||||||
|
|
||||||
@ -94,7 +94,7 @@ When updating the playbook, refer to [the changelog](CHANGELOG.md) to catch up w
|
|||||||
|
|
||||||
This playbook sets up your server using the following Docker images:
|
This playbook sets up your server using the following Docker images:
|
||||||
|
|
||||||
- [matrixdotorg/synapse](https://hub.docker.com/r/matrixdotorg/synapse/) - the official [Synapse](https://github.com/matrix-org/synapse) Matrix homeserver
|
- [matrixdotorg/synapse](https://hub.docker.com/r/matrixdotorg/synapse/) - the official [Synapse](https://github.com/matrix-org/synapse) Matrix homeserver (optional)
|
||||||
|
|
||||||
- [instrumentisto/coturn](https://hub.docker.com/r/instrumentisto/coturn/) - the [Coturn](https://github.com/coturn/coturn) STUN/TURN server (optional)
|
- [instrumentisto/coturn](https://hub.docker.com/r/instrumentisto/coturn/) - the [Coturn](https://github.com/coturn/coturn) STUN/TURN server (optional)
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user