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

Replaced keepEvents with defaultKeepEvents and meetingKeepEvents #11681

Merged
merged 1 commit into from Mar 18, 2021

Conversation

antobinary
Copy link
Member

What does this PR do?

  1. Allows for meetings to override the defaultKeepEvents property (formerly keepEvents Created property keepEvents at bbb-web to make redis record the event… #6385 ) by passing meetingKeepEvents= true or false

  2. I set defaultKeepEvents to false, which is reverting enable post_events by default by setting keepEvents=true #10097 , cc @jfederico

Note that defaultKeepEvents is only used in case meetingKeepEvents is not passed.

Closes Issue(s)

none

Motivation

We would like to have finer control over which meetings' events are recorded. Until now you would either keep events from all or none of the meetings

More

@antobinary
Copy link
Member Author

I followed up with @jfederico and he gave thumbs up to merge it!

@antobinary antobinary merged commit 67bc575 into bigbluebutton:develop Mar 18, 2021
antobinary added a commit that referenced this pull request Mar 22, 2021
@antobinary antobinary deleted the keepEvents branch April 3, 2021 19:46
keevan added a commit to catalyst/moodle-mod_bigbluebuttonbn that referenced this pull request Jun 3, 2021
As per bigbluebutton/bigbluebutton#11681 and https://github.com/bigbluebutton/bigbluebutton.github.io/pull/239/files it seems that this new option was added to let the client control whether or not the data should be stored. The data needs to be stored if meeting stats are required so it can be sent back from the BBB server
keevan added a commit to catalyst/moodle-mod_bigbluebuttonbn that referenced this pull request Jun 3, 2021
As per bigbluebutton/bigbluebutton#11681 and https://github.com/bigbluebutton/bigbluebutton.github.io/pull/239/files it seems that this new option was added to let the client control whether or not the data should be stored. The data needs to be stored if meeting stats are required so it can be sent back from the BBB server
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants