Releases: blindsidenetworks/scalelite
v1.1.5.1
v1.1.5
v1.1.5-beta.1
Release: major 1, minor 1, revision 5, beta 1
v1.1.4
Release notes - Scalelite - Version 1.1.4
Hot-fix
SL-180 Error while rejoining an existing meeting from moodle
Bug
SL-148 ERROR: prepared statement already exists # 213
SL-147 getRecordings error with PG cluster #213
Task
SL-35 Create rake task that creates multiple BBB servers from a YAML file
v1.1.3
v1.1.2
Release notes - Scalelite - Version 1.1.2
Bug
SL-141 SL fails to import recordings due permissions
New Feature
SL-130 Filter getRecordings request based on the recording state
SL-129 Filter getRecordings request based on meta parameters
SL-98 Implement core post_event scripts
v1.1.1.0
Release notes - Scalelite - Version 1.1.1.0
This is a minor patch for v1.1.1. The only change is that asides of sending logs to STDOUT (which was hard-coded in the image), can now be set through ENV variables to true/false when using some other mechanism for externalising logs. It is set to true
by default in the Dockerfile, so the behaviour does not affect current deployments.
Bug
SL-133 Logs were always sent to STD_OUT
v1.1.1
v1.1
This release requires to run migrations
docker exec -t scalelite-api bundle exec rake db:migrate
Bug
- Recordings that are reprocessed in BBB should override the one already imported in SL
Improvement - Updated main image to
bionic230
. - Nginx is now fixed to
1.18.0-r13
. - Created general image with all rails components and extended images on alpine and amazonlinux.
- Added LOAD_JOIN_BUFFER_TIME=0 for breakout rooms.
- Parameters coming from 3rd parties will now get overridden.
- Scalelite Poller execute tasks in parallel.
- Scalelite is now compatible with
BigBlueButton 2.3
recordings.
New Feature
- Recording ready notification feature has been added.
- Recordings can be imported as unpublished by default now.
- A New state for servers has been added to retain existing meetings and not accept anymore meeting creation requests
- The server has a new attribute called
state
which tracks the server state. The Server can have either of the three states:enabled/cordoned/disabled
. - The change would not affect any existing servers, unless there is a state change for them but would be applicable for all the newly added servers.
- The
enabled
attribute of servers will not be considered anymore once the state attribute has been introduced for all new or existing servers. - See README for details on the functions of each server state.
- The server has a new attribute called
Task
- Replaced GitLab CI pipeline with a GitHub Actions CI workflow.
- Extended images are automatically built by GitHub Actions, this includes an image based on amazonlinux.
- [Security] Updated docker containers for CVE-2021-3449 and CVE-2021-3450.