Given that the web component’s config.js file is generated automatically, I’m wondering what’s the best way to modify those settings such that they’re preserved when upgrading.
I know some of the values come from the .env file, but what if I want to set other options? If the copy in the .jitsi-meet-cfg directory is modified directly, the changes are lost the next time new .env settings need to be deployed. If I use a Docker bind mount, then settings added in new releases won’t be included unless I manually keep the changes in sync.
Is there a better way?