Customizing Jitsi

[A Former User]

Does anyone have Jitsi branded using config.js, are there limitations given Cloudron's read-only file system?

I guess it's not possible to edit close3.html to redirect users elsewhere following call?

[nebulon]

@nothing the only customization which is currently supported are changing the /app/data/jitsi-meet-config.js file and thus whatever the app supports there in changes. The rest of the code assets are in read-only filesystem as you suspected.

[robi]

Try the close page:

// Enabling the close page will ignore the welcome page redirection when
// a call is hangup.
// enableClosePage: false,

[girish]

I put a note in the docs here - https://docs.cloudron.io/apps/jitsi/#custom-configuration

[g00d]

I see changes to Jitsi config.js are possible via jitsi-meet-config.js.

I am wondering if changes to the deprecated but still used interface_config.js file are possible in Cloudron?

Since not all options are available in config.js yet, since they have not been completely moved from the old interface configuration file.

So, is there any web to modify those settings in a Cloudron Jitsi installation?

For example, the displayed APP_NAME, etc.

I tried placing a interface_config.js inside /app/data along the other config file, but without any success.

Thanks

[nebulon]

Tweaking via interface_config.js is indeed not supported by the package currently.

[dev-cb]

@nebulon said in Customizing Jitsi:

Tweaking via interface_config.js is indeed not supported by the package currently.

Do you think that might change soonish?

[nebulon]

@dev-cb as of https://github.com/jitsi/jitsi-meet/blob/master/interface_config.js#L4 the file is still considered deprecated. So I don't think it makes sense to support this, if those config options, if relevant for future versions, move into the the other config.js over time.

[dev-cb]

@nebulon I noticed that the deprecated notice was added in Mar, 2021.

Unfortunately there is no official development roadmap so it might just take much longer.