synapse

History

Jorik Schellekens 839f9b9231 One shot demo server startup Configure the demo servers to use untrusted tls certs so that they communicate with each other. This configuration makes them very unsafe so I've added warnings about it in the readme.		2019-06-17 16:24:28 +01:00
..
.gitignore	Clean up gitignores (#4688 )	2019-02-20 11:10:50 +00:00
clean.sh	Fix the cleanup script to use the right $DIR	2015-08-12 09:39:07 +01:00
README	One shot demo server startup	2019-06-17 16:24:28 +01:00
start.sh	One shot demo server startup	2019-06-17 16:24:28 +01:00
stop.sh	Reference Matrix Home Server	2014-08-12 15:10:52 +01:00
webserver.py	Create a temporary upload service server side (by hacking demos/webserver.py) and client side with an angularjs service component.	2014-08-14 18:38:56 +02:00

README

DO NOT USE THESE DEMO SERVERS IN PRODUCTION

Requires you to have done:
    python setup.py develop


The demo start.sh will start three synapse servers on ports 8080, 8081 and 8082, with host names localhost:$port. This can be easily changed to `hostname`:$port in start.sh if required.

To enable the servers to communicate untrusted ssl certs are used. In order to do this the servers do not check the certs
and are configured in a highly insecure way. Do not use these configuration files in production.

stop.sh will stop the synapse servers and the webclient.

clean.sh will delete the databases and log files.

To start a completely new set of servers, run:

    ./demo/stop.sh; ./demo/clean.sh && ./demo/start.sh


Logs and sqlitedb will be stored in demo/808{0,1,2}.{log,db}



Also note that when joining a public room on a differnt HS via "#foo:bar.net", then you are (in the current impl) joining a room with room_id "foo". This means that it won't work if your HS already has a room with that name.