ernolf
January 11, 2024, 8:11pm
81
bb77:
I have tried all possible combinatons like…
"home_mode_enable"
"home_mode_enable=false"
"home_mode_enable=true"
"extra_params=--o:home_mode.enable=true"
"extra_params=--o:home_mode.enable=false"
etc…
…and I could not get the nag screen to appear, even without passing the variable at all. So maybe they finally removed it for good…?!?
But it should be
home_mode.enable
instead of home_mode_enable
and if you host it as a standalone server, you have to set this from false
to true
in your /etc/coolwsd/coolwsd.xml
:
<home_mode>
<enable desc="Enable more configuration options for home users" type="bool" default="false">true</enable>
</home_mode>
and I can confirm that it suppresses the nag screen. As soon as I set the value back to false and restart the coolwsd, the nag screen reapears the next time I call it up.
Much and good luck
ernolf
2 Likes
bb77
January 12, 2024, 9:11am
82
I use the standalone Docker container: collabora/code
I have passed the environment variable in all possible ways, and I still have no idea if it does anything.
Last time I tried, I started the container as follows:
docker run -t -d -p 127.0.0.1:9980:9980 --name=collabora \
-e "aliasgroup1=https://cloud.mydomain.tld:443,https://cloud\\.mydomain\\.tld:443" \
-e "username=admin" -e "password=super_secret_password" \
-e "lang=de_CH" -e "dictionaries=de_CH de_DE en_GB en_US" \
-e "extra_params=--o:home_mode.enable=true" \
--restart always collabora/code
Anyways, my point was that no matter how I start the container, I don’t get the nag screen, even if I don’t pass the extr_parms
environment variable.
Ah and the coolwsd.xml
in the container always says the following:
<home_mode>
<enable desc="Enable more configuration options for home users" type="bool" default="false">false</enable>
</home_mode>