Upgrade from V2.3-alpha8 to V2.4-beta3: Override feature does not work
25 views
Skip to first unread message
Wolfgang Pein
unread,
Sep 2, 2021, 3:10:52 PM9/2/21
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Sign in to report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to BigBlueButton-Setup
Hi all,
I successfully upgraded BBB V2.3-alpha8 to BBB V2.4-beta3 by use of the bbb-install.sh script. In V2.3 I have made a number of changes to BBB original conf files e.g. "SkipCheck: true".
I did this before running the bbb-install.sh script!!
However it seems that these changes in override files have not been applied to the BBB conf files i.e. file /usr/share/meteor/bundle/programs/server/assets/app/config/settings.yml the setting still contains the default value (SkipCheck: false).
What am I missing? Does override not work in my setup/upgrade?
Thanks
Wolfgang
Philipp Memmel
unread,
Sep 2, 2021, 3:19:33 PM9/2/21
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Sign in to report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to bigbluebu...@googlegroups.com
Sure, you got the spelling right? It's "skipCheck", not "SkipCheck". Works for me like this...
Pypo
Wolfgang Pein
unread,
Sep 2, 2021, 3:44:08 PM9/2/21
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Sign in to report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to BigBlueButton-Setup
Sorry, typo in my posting - I used skipCheck (small s at the beginning) and not SkipCheck !!!
You do not have permission to delete messages in this group
Copy link
Report message
Sign in to report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to bigbluebu...@googlegroups.com
Ah, I might now just understand your problem:
These changes are not "applied" to the other config files on
installation, but the different components of BBB read from both the
override files and the standard config files:
Whenever the override file contains a key this key's value is preferred
over the value which is contained in
/usr/share/meteor/bundle/.../settings.yml
That's what is meant by "override": The content of
/usr/share/meteor/.../settings.yml will still be the same. But the keys
in /etc/bigbluebutton/bbb-html5.yml are "more powerful". Have you
checked if the settings are applied in a real BBB session on that node?
> *I did this before running the bbb-install.sh script!!*
>
> However it seems that these changes in override files have
> not been applied to the BBB conf files i.e. file
> /usr/share/meteor/bundle/programs/server/assets/app/config/settings.yml
> the setting still contains the default value (SkipCheck: false).
>
> What am I missing? Does override not work in my setup/upgrade?
>
> Thanks
> Wolfgang
>
>
You do not have permission to delete messages in this group
Copy link
Report message
Sign in to report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to 'Philipp Memmel' via BigBlueButton-Setup
Great comment! You are absolutely right: it was my believe that the
original conf file will be "overwritten" by the content of the override
files.
Maybe the documentation should be more precise and explain this
behaviour (I would call it "overruling")? Why has it been implemented
this way?
I checked again and indeed: the skipCheck = true setting has been
properly applied - no microfone check at the beginning of a session!!!