* 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_RECORDINGpull/1335/head^2
parent
a2b86a0f9a
commit
7890183b9f
Loading…
Reference in new issue