Fix dataChange2 events not reaching Matrix bridge in production-like setup
Fix dataChange2 events not reaching Matrix bridge in production-like setup
Start the matrix-bridge in the API process so the dataChange2 events that fire in the API process make their way over to the matrix-bridge.
Before the matrix-bridge was just running in the web process, which didn't see any dataChange2 events because the API is served by the separate process where all of the action happens.
Technically, we only need matrix-bridge/lib/gitter-bridge
running in the web.js
process but the matrix-appservice-bridge
doesn't allow us to use the API calls without running bridge.run
.
Dev notes
Debugging on beta why Gitter messages aren't creating Matrix rooms:
$ ssh beta-webapp-01.beta.gitter
$ systemctl stop gitter-web-1
$ systemctl start gitter-web-1
# Follow the latest log stdout for the process
$ journalctl -u gitter-web-1 -f
$ systemctl stop gitter-api-1
$ systemctl start gitter-api-1
# Follow the latest log stdout for the process
$ journalctl -u gitter-api-1 -f
Edited by Eric Eastwood