cdist-contrib/type/__jitsi_meet/gencode-remote

#!/bin/sh -e

if grep -qE "^__file/etc/nginx" "${__messages_in}"; then
	echo "service nginx reload"
fi

if grep -qE "^(__line/jitsi_jicofo_secured_domains|(__file|__link)/etc/prosody/conf.d/|__file/etc/jitsi/jicofo/jicofo.conf)" "${__messages_in}"; then
  echo "systemctl restart prosody"
  echo "systemctl restart jicofo"
  echo "systemctl restart jitsi-videobridge2"
fi
Import evilham's jitsi types as-it 2021-01-11 10:52:14 +00:00			`#!/bin/sh -e`

			`if grep -qE "^__file/etc/nginx" "${__messages_in}"; then`
			`echo "service nginx reload"`
			`fi`
[__jitsi_meet*] Add parameters for secure domains This is done with slight adaptations from the official guide at https://jitsi.github.io/handbook/docs/devops-guide/secure-domain Amongst other changes, we rely on Prosody's configuration parser only overwriting the parts of a VirtualHost that are explicitly specified in "later appearing" (lexicographically speaking) files. This allows us to let Jitsi manage the main config file and adding the few customisations on top of it. We also use the Plaintext authenticator as this is enough atm and is the easiest to manage in an idempotent fashion; support for other authentication mechanisms is possible, see Prosody's documentation for that. 2021-05-10 14:40:46 +00:00
[__jitsi_meet*] Make rooms on different domains not equivalent This is a backwards-compatible change. We switch the approach from "treat all domains as if they were the main domain" to: "each domain has its own prosody settings". This works perfectly fine, even with secured domains. There is a caveat with secured domains, in that they use the main domain to log in; this means that users are shared across all domains (as they were before this commit). This is due to jicofo refusing to start meetings from a domain that is not configured, and it only accepting one domain. Right now, this is acceptable, however we could want to authenticate against e.g. different LDAP / IMAP servers in the future, so this would need addressing at that stage. Probably the best way to solve it is by patching jicofo, so it accepts starting conferences from multiple domains and getting that patch upstream. Sponsored by: camilion.eu, eXO.cat 2022-04-21 11:20:30 +00:00			`if grep -qE "^(__line/jitsi_jicofo_secured_domains\|(__file\|__link)/etc/prosody/conf.d/\|__file/etc/jitsi/jicofo/jicofo.conf)" "${__messages_in}"; then`
[__jitsi_meet*] Add parameters for secure domains This is done with slight adaptations from the official guide at https://jitsi.github.io/handbook/docs/devops-guide/secure-domain Amongst other changes, we rely on Prosody's configuration parser only overwriting the parts of a VirtualHost that are explicitly specified in "later appearing" (lexicographically speaking) files. This allows us to let Jitsi manage the main config file and adding the few customisations on top of it. We also use the Plaintext authenticator as this is enough atm and is the easiest to manage in an idempotent fashion; support for other authentication mechanisms is possible, see Prosody's documentation for that. 2021-05-10 14:40:46 +00:00			`echo "systemctl restart prosody"`
			`echo "systemctl restart jicofo"`
			`echo "systemctl restart jitsi-videobridge2"`
			`fi`