I’ve been trying to get Jitsi deployed as an Azure container group (via terraform, not the docker compose aci integration), using the containers specified in the docker-compose.yml. I’m hitting a few snags with the prosody configuration. (I think the other containers are fine, but we’ll see.)
Prosody doesn’t seem to pick up the Jicofo component secret from the environment:
component_secret = “<no value>”
Is it just Lua code, meaning I could pull it in with os.getenv?
Prosody doesn’t generate certificates–/config/certs is empty. When I run everything locally, I get certificates for meet.jitsi and auth.meet.jitsi. I think these are self-signed certs, so I probably could just copy them over to the Azure file share holding my config file? Or generate a cert with letsencrypt?
The JVB password appears to be stored in plaintext in sip-communicator.properties. Will it parse a reference to an environment variable instead?