tileradotorg/synapse
1
0
Fork 0
forked from MirrorHub/synapse
Code Pull requests Activity

Add some documentation about high performance storage

Browse source
This commit is contained in:
kaiyou 2018-02-08 19:48:53 +01:00
parent 63fd148724
commit 58df3a8c5d
1 changed files with 7 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
contrib/docker/README.md
View file

@ -31,11 +31,11 @@ Then, to run the server:
docker-compose up -d docker-compose up -d
``` ```
In the case you specified a custom path for you configuration file and wish to In the case you specify a custom path for you configuration file and wish to
generate a fresh ``homeserver.yaml``, simply run: generate a fresh ``homeserver.yaml``, simply run:
``` ```
docker-compose run --rm synapse generate docker-compose run --rm -e SYNAPSE_SERVER_NAME=my.matrix.host synapse generate
``` ```
If you do not wish to use Compose, you may still run this image using plain If you do not wish to use Compose, you may still run this image using plain
@ -62,6 +62,11 @@ The image expects a single volume, located at ``/data``, that will hold:
* the SQLite database if you do not configure postgres; * the SQLite database if you do not configure postgres;
* the appservices configuration. * the appservices configuration.
You are free to use separate volumes depending on storage endpoints at your
disposal. For instance, ``/data/media`` coud be stored on a large but low
performance hdd storage while other files could be stored on high performance
endpoints.
In order to setup an application service, simply create an ``appservices`` In order to setup an application service, simply create an ``appservices``
directory in the data volume and write the application service Yaml directory in the data volume and write the application service Yaml
configuration file there. Multiple application services are supported. configuration file there. Multiple application services are supported.