Changing the default value from http to https. At this point the playback links generated in the recording metadata.xml files should default to httpS protocol
v2.17.0-alpha.1
---
* feat: add `enabled` flag to SFU modules, default to true
* fix(livekit): do not sync stale egress instances
* build(livekit): add LiveKit submodule to base configuration
If the user has no access to the docker socket, root privileges are
required. This fix adds a missing sudo so docker attach works.
Co-authored-by: Daniel Schreiber <daniel.schreiber@hrz.tu-chemnitz.de>
* Change: Add a new console class that allow us show extra info passed to log
* detailed logs: use env var + enable by default on development
* remove duplicated code
* Prevent negative array length when padding level name + Simplify condition using optional chaining
---------
Co-authored-by: Ramón Souza <contato@ramonsouza.com>
* Option to disable new chat features like edit, delete, reply and send-reaction using the param disabledFeatures"
* Revert documentation while recording portion is not ready
If the build system for packages has a umask of `0077`, cloned
repositories will have no permissions for group and other. If build
scripts just copy files, permissions will persist. This commit fixes
permissions for some files which otherwise prevents startup
`bbb-graphql-server.service` and `bbb-graphql-middleware.service`.
Co-authored-by: Daniel Schreiber <daniel.schreiber@hrz.tu-chemnitz.de>
Slides are alwas requested cross domain in a cluster setup. There is no
authentication required for the slides, so we can just allow requests
from anywhere.
Co-authored-by: Daniel Schreiber <daniel.schreiber@hrz.tu-chemnitz.de>
It introduces the graphql prop `reactions` to the type `chat_message_public` and `chat_message_private`.
It also add two mutations `chatSendMessageReaction` and `chatDeleteMessageReaction`.
* feat(chat): improve messages rendering
This commit adds memoization and comparsion functions to the chat pages
and chat messages to prevent whole chat re-renders and unnecessary
message re-renders caused by React's default shallow comparsion mechanism.
The comparsion functions ensure that only the pertinent message attributes
trigger a component's re-render.
Messages sent by a user are not updated (re-rendered) when their role
change. In other words, the chat messages reflect the user's role at the
time the message was sent. Altering the message to reflect the user's
current role could confuse participants, as it would modify the context
of the past conversation. This behavior has been validated by the UI/UX
team and brings benefits such as performance improvements and consistent
behavior with how playback handles such messages.
* fix linter errors
v2.17.0-alpha.0
---
* feat(livekit): add track egress support
* feat(livekit): webhooks module
* feat(livekit): server side BBB <-> LiveKit event sync
* refactor(livekit): rename GenerateWebRtcToken* to GenerateLiveKitToken*
* feat: base-manager may opt out of connecting to mcs-core
* build(livekit-server-sdk): v2.6.2
It introduces the mutations:
chatEditMessage
chatDeleteMessage
The type chat_message receive two new fields:
updatedAt
deletedAt
A new table chat_message_history was introduced to store the previous version of an edited or deleted message.
When removed the message is not deleted, but the content become null and deletedAt populated. So the idea is to show "This message was removed" in the client.
