2017-09-28 12:12:47 +02:00
|
|
|
|
2019-10-18 11:23:33 +02:00
|
|
|
# Synapse Docker
|
2018-05-16 11:10:31 +02:00
|
|
|
|
2019-10-18 11:23:33 +02:00
|
|
|
### Configuration
|
2018-02-08 21:55:35 +01:00
|
|
|
|
|
|
|
A sample ``docker-compose.yml`` is provided, including example labels for
|
2018-05-16 11:10:31 +02:00
|
|
|
reverse proxying and other artifacts. The docker-compose file is an example,
|
|
|
|
please comment/uncomment sections that are not suitable for your usecase.
|
2018-02-08 21:55:35 +01:00
|
|
|
|
|
|
|
Specify a ``SYNAPSE_CONFIG_PATH``, preferably to a persistent path,
|
2019-10-18 11:23:33 +02:00
|
|
|
to use manual configuration.
|
|
|
|
|
|
|
|
To generate a fresh `homeserver.yaml`, you can use the `generate` command.
|
|
|
|
(See the [documentation](../../docker/README.md#generating-a-configuration-file)
|
|
|
|
for more information.) You will need to specify appropriate values for at least the
|
|
|
|
`SYNAPSE_SERVER_NAME` and `SYNAPSE_REPORT_STATS` environment variables. For example:
|
2017-09-28 12:12:47 +02:00
|
|
|
|
|
|
|
```
|
2019-10-18 11:23:33 +02:00
|
|
|
docker-compose run --rm -e SYNAPSE_SERVER_NAME=my.matrix.host -e SYNAPSE_REPORT_STATS=yes synapse generate
|
2017-09-28 12:12:47 +02:00
|
|
|
```
|
|
|
|
|
2019-10-18 11:23:33 +02:00
|
|
|
(This will also generate necessary signing keys.)
|
|
|
|
|
2018-02-08 21:55:35 +01:00
|
|
|
Then, customize your configuration and run the server:
|
|
|
|
|
|
|
|
```
|
|
|
|
docker-compose up -d
|
|
|
|
```
|
|
|
|
|
2018-05-21 15:45:33 +02:00
|
|
|
### More information
|
2018-02-08 20:53:12 +01:00
|
|
|
|
2018-08-03 10:15:19 +02:00
|
|
|
For more information on required environment variables and mounts, see the main docker documentation at [/docker/README.md](../../docker/README.md)
|
2024-11-22 13:35:03 +01:00
|
|
|
|
|
|
|
**For a more comprehensive Docker Compose example showcasing a full Matrix 2.0 stack, please see
|
|
|
|
https://github.com/element-hq/element-docker-demo**
|