Support Jitsi information from client .well-known
It can be useful for the homeserver to support a dedicated Jitsi instance instead of requiring that all their users change/update their configs manually.
This commit is contained in:
parent
2b6cbae4a7
commit
2ec7f2290c
3 changed files with 79 additions and 1 deletions
|
@ -40,6 +40,7 @@ import ToastStore from "./stores/ToastStore";
|
|||
import {IntegrationManagers} from "./integrations/IntegrationManagers";
|
||||
import {Mjolnir} from "./mjolnir/Mjolnir";
|
||||
import DeviceListener from "./DeviceListener";
|
||||
import {Jitsi} from "./widgets/Jitsi";
|
||||
|
||||
/**
|
||||
* Called at startup, to attempt to build a logged-in Matrix session. It tries
|
||||
|
@ -604,6 +605,9 @@ async function startMatrixClient(startSyncing=true) {
|
|||
// This needs to be started after crypto is set up
|
||||
DeviceListener.sharedInstance().start();
|
||||
|
||||
// Now that we have a MatrixClientPeg, update the Jitsi info
|
||||
await Jitsi.getInstance().update();
|
||||
|
||||
// dispatch that we finished starting up to wire up any other bits
|
||||
// of the matrix client that cannot be set prior to starting up.
|
||||
dis.dispatch({action: 'client_started'});
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue