This addes the transcipts path to the list of static items that should
be allowed by nginx.
Fixes#1427
Signed-off-by: Ben Magistro <koncept1@gmail.com>
If JAAS_APP_ID is set, the config will be updated to point to the
production JaaS deployment for the given App ID.
If JAAS_USE_STAGING is set to a truthy value the configuration will
point to stage.8x8.vc rather than the production 8x8.vc.
It is expected to be "focus" in a number of places inside lib-jitsi-meet
and that won't change anytime soon.
Allowing users to change it is just asking for trouble.
Fixes: https://github.com/jitsi/lib-jitsi-meet/issues/2191
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.
* 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"
* Fixing ENABLE_RECORDING issue
In https://github.com/jitsi/docker-jitsi-meet/pull/1372, I made a change to allow the web component to set ENABLE_RECORDING and still enable recording (in order to have "service recording" disabled but Dropbox recording enabled.
I failed to notice that the ENABLE_RECORDING environment variable is also used in Prosody (and in a number of places) as a global switch.
With the new variable semantic (as proposed in #1372), in order to know if Jibri must be enabled or not, we need 3 variables (ENABLE_RECORDING, DROPBOX_APPKEY and ENABLE_LIVESTREAMING).
This means we should also propagate those variables to Prosody.
To be honest, having the "DROPBOX_APPKEY" forwarded to Prosody just to know if we should enable or disable recording is a bit weird.
So I feel it is a better idea to revert back the meaning of "ENABLE_RECORDING" to be a global switch.
I'm therefore reverting back to old behaviour and adding a new environment variable (ENABLE_SERVICE_RECORDING) that allows turning on or off the "service recording".
* Setting ENABLE_SERVICE_RECORDING default value to ENABLE_SERVICE_RECORDING
Ben Magistro
Aaron van Meerten
lala
Saúl Ibarra Corretgé
loli10K
Zhen Guang
simon
HannesOberreiter
Jaya Allamsetty
Saúl Ibarra Corretgé
Kurt Garloff
Jaya Allamsetty
Cedric Roijakkers
Daniel McAssey
emrah
Aaron van Meerten
Oana Emilia Ianc
Debendra Oli
Charles Zablit
Ben Banfield-Zanin
David Négrier
damencho