Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

jitsi-meet-electron 2022.3.1 how to set serverURL in users configuration file? #740

Open
tuxcrafter opened this issue Mar 26, 2022 · 7 comments
Labels
prs-welcome Pull Requests are welcome

Comments

@tuxcrafter
Copy link

Hello everybody,

I used to be able to configure the serverURL and name in the /home/$USER/.config/Jitsi Meet/config.json file before starting Jitsi meet for the first time and have it go to our own server. I can not figure out how to do this with jitsi-meet-electron 2022.3.1

Can somebody help me and tell me how to set these options in a configuration file?

I can only find tickets from 2018 where people where grateful for adding the serverURL option...

Thank you in advance.

@csett86
Copy link
Member

csett86 commented Mar 27, 2022

Unfortunately we had to migrate away from electron-storage (which was the config backend reading from config.json) to the electron native localStorage in #638 and then remove electron-storage completely in #668. I can assure you that I did not take that decision lightly (and tried a lot to get electron-storage working under newer electron versions, but failed), as it also meant breaking users settings if they did not update within 2.5 months.

Chromiums (and thus Electron) localStorage is backed by a LevelDB, but a quick search did not result in tooling available to interact with it outside of the browser.

So for now I don't see a possibility to feed the serverURL during install, unfortunately.

@tuxcrafter
Copy link
Author

Thank you for answering! That is said news!! What was the latest version with electron-storage backend? Would it be possible somehow to ship a LevelDB file with a preset serverURL and maybe a name in the users profile? /etc/skel type of thing as well.

@saghul
Copy link
Member

saghul commented Mar 28, 2022

One way to do it might be to detect a config file in the user data dir and if found override the default config with it. This would only work for the first launch, since I think silently changing settings in between launches can lead to dangerous situations otherwise.

If you are up for it a PR would be welcome, we can iron out the details there.

@tuxcrafter
Copy link
Author

That would be great, we still have the config.json, if that could be imported and used to configure the LevelDB that would be great.

# cat /home/$USER/.config/Jitsi\ Meet/config.json 
{
    "persist:root": "{\"onboarding\":\"{\\\"onboardingShown\\\":[\\\"onboarding-modal\\\",\\\"conference-url\\\",\\\"settings-drawer-button\\\",\\\"name-setting\\\",\\\"email-setting\\\",\\\"start-muted-toggles\\\",\\\"server-setting\\\",\\\"server-timeout\\\",\\\"always-on-top-window\\\"]}\",\"recentList\":\"{\\\"recentList\\\":[]}\",\"settings\":\"{\\\"alwaysOnTopWindowEnabled\\\":true,\\\"email\\\":\\\"\\\",\\\"name\\\":\\\"John Doe\\\",\\\"serverURL\\\":\\\"https://jitsi.example.com/\\\",\\\"startWithAudioMuted\\\":false,\\\"startWithVideoMuted\\\":false}\",\"_persist\":\"{\\\"version\\\":-1,\\\"rehydrated\\\":true}\"}"
}

@saghul
Copy link
Member

saghul commented Mar 28, 2022

That (used to) persist the entire state, including window position and the like. I was thinking about something which would override what is currently on config.js.

@tuxcrafter
Copy link
Author

Any updates on this? How to configure the serverURL for our users?

@saghul
Copy link
Member

saghul commented Jun 1, 2022

Nobody is working on this. I do not have plans to do so. a PR would be welcome.

@saghul saghul added the prs-welcome Pull Requests are welcome label Jul 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
prs-welcome Pull Requests are welcome
Projects
None yet
Development

No branches or pull requests

3 participants