Updating to OpenTalk Controller v0.31.0

New mandatory [frontend] section

The controller now requires a [frontend] section defining the frontend base_url. It is used for generating links (e.g. in invite emails) and as the default value for the CORS header.

[frontend]
base_url = "https://example.com"

RabbitMQ is now optional

The [rabbit_mq] section is no longer part of the base configuration. It is only required when using services that interact with the controller (e.g. the SMTP mailer, recorder or SIP call-in). If you don't use any of these, the section can be removed.

New optional [operator_information] section

Information about the operator responsible for user-facing communication and legal disclosure can now be configured:

#[operator_information]
#data_protection_url = "https://example.com/data-protection"
#support_phone_number = "+493012345678"
#support_email_address = "support@example.com"

New optional [roomserver] section

An experimental roomserver can now be configured. When enabled, the built-in signaling endpoints are replaced by the roomserver signaling endpoints, so the deployed frontend has to be compatible.

#[roomserver]
#url = "http://localhost:11333"
#api_token = "secret"
#[roomserver.modules.chat]
#[roomserver.modules.e2ee]
#[roomserver.modules.livekit]
#api_key = "devkey"
#api_secret = "secret"
#public_url = "http://localhost:7880"
#service_url = "http://localhost:7880"
#[roomserver.modules.echo]
#[roomserver.modules.polls]
#[roomserver.modules.timer]

New optional settings

• defaults.timezone — the timezone used by the system and as the users' default, in IANA format (e.g. "Europe/Berlin"). When unset, the TZ environment variable and the OS are consulted, finally falling back to "Etc/UTC".
• [websocket_rate_limit] — token-bucket based rate limiting for websocket messages (enabled by default with tokens_per_second = 10 and token_bucket_size = 30).