Confusing LiveKit Documentation and TUWUNEL_LIVEKIT_URL not supported ?

[Morgan-SL-PUP]

Im setting up Tuwunel currently and Im a bit confused on the Documentation regarding setting the Livekit URL for Tuwunel.

In the Documentation for the Livekit Setup it says to add it like this:

[[global.well_known.rtc_transports]]
type = "livekit"
livekit_service_url = "https://matrix-rtc.yourdomain.com"

But the Documentation of the Toml File states:

If you're looking to setup Element Call / MatrixRTC with Livekit,
you should not use this option and instead set livekit_url.

So what is the correct option know?

Additionally I tried setting it via an Environment Variable named "TUWUNEL_LIVEKIT_URL" since that Format worked for the other options but I guess that is not supported and I have to do it via the toml file ?

[utop-top]

You simply need to learn how to configure the declarations on your proxy tool.https://github.com/element-hq/element-call/blob/livekit/docs/self-hosting.md

[Morgan-SL-PUP]

You simply need to learn how to configure the declarations on your proxy tool.https://github.com/element-hq/element-call/blob/livekit/docs/self-hosting.md

I have Livekit configured as per the instructions behind my proxy. Im asking which configuration option in Tuwunel would be the correct one. Do I need set "livekit_url" since im setting it up with liviekt or do I need to add the "livekit_service_url".

The Documentation of Element Call ist also referencing "livekit_service_url". Im just confused about the existence of "livekit_url" in the toml file, since it specifically states to not use "livekit_service_url" with livekit.

Im Deploying the well known files via the builtin function of tuwunel btw.

And the Question still Remains if those Configurations can be done via environment Variables, instead of the toml file

[BVollmerhaus]

Both methods of configuring LiveKit accomplish the same thing, i.e. they cause Tuwunel to include the

{
  "org.matrix.msc4143.rtc_foci": [
    {
      "type": "livekit",
      "livekit_service_url": "https://example.org/livekit/jwt"
    }
  ]
}

information required for MatrixRTC in its well-known delegation response (assuming you let Tuwunel serve that).

As LiveKit needs to be configured quite frequently, the livekit_url option was introduced to make it a bit simpler:

# Custom MatrixRTC transports.
#
# [...]
#
# This option was previously the only way to configure a Livekit
# transport. It has been superseded by `livekit_url`.

Lastly, the environment variable requires a TUWUNEL_WELL_KNOWN__ prefix, since it is part of the [global.well-known] table.