It's not enabled by default and there is no way to disable it any
longer.
We keep setting the flags in config.js though, this is so old mobile
versions without the new default behavior can enable it.
The new variable has a better purposed name, and supports a comma
separated list of IPs instead of a single one, which should help those
running split-horizon setups.
* Migrating configuration to use secure octo configuration by default
Adding a new JVB_OCTO_RELAY_ID to configure videobridge.relay.relay-id (with a fallback to the old JVB_OCTO_BIND_ADDRESS to be used as relay-id)
* Adding a configuration check to verify that Octo cannot be enabled without the ENABLE_COLIBRI_WEBSOCKET environment variable set to "1"
Use default values everywhere so they don't need to be specified in the
.env file.
This makes the default .env file much smaller (the larger config options
are documented in the handbook) and should make it easier to port the
setup to runtimes other than Docker Compose.
* jicofo: add optional XMPP_PORT value
* include compose and env example for XMPP_PORT
* extends use of the XMPP_PORT property
* fix compose to use default
* re-commenting XMPP_PORT value
* include XMPP_PORT in compose for all services
* always use $XMPP_PORT, value defaulted in template
* missing JVB setting
We noticed that websocket were broken with this config.
We believe that the translation from old config to new config in [this commit](130eb551a7 (diff-6f9b0c296a7ff789834c1414349f64f956f2b64df6e405fd45f62c6a11edad3fL34)) didn't translate it well.
We are actually wondering what does private stands for in this context.
With this change, we can confirm that wss works again as expected.
Aaron van Meerten
Saúl Ibarra Corretgé
David Négrier
Ben Banfield-Zanin
Saúl Ibarra Corretgé
wfleischer
Daniel McAssey
Aaron van Meerten
Holger Pandel
Артем
Prayag Singh
Pierre Ozoux
bbaldino