v1.3-beta.2

Release notes - Scalelite - Version 1.3.beta.2

Enhancements:

SL-210: New rake tasks for managing servers and meetings

Update a server: ./bin/rake servers:update[id,secret,loadMultiplier]
List all meetingIds running in specific/all servers: ./bin/rake servers:meeting_list["serverID1 serverID2 serverID3"]
List all/specific meetings running in BigBlueButton servers: ./bin/rake meetings:list["meetingId1 meetingId2 meetingId3"]
Get meeting details of a meeting running in BigBlueButton server: ./bin/rake meetings:info[meetingId]
End all/specific meetings running in BigBlueButton servers: ./bin/rake meetings:end["meetingId1 meetingId2 meetingId3"]

v1.3-beta.1

Release notes - Scalelite - Version 1.3.beta.1

Bug:

• SL-183: Problem joining meeting via Scalelite using POST #592
• SL-204: /scalelite_batch_import.sh : add group scalelite-spool #646
• SL-213: When a recording is unpublished, the flag published is set to false, but the state remains as published, this makes the getRecordng requests with filter unpublished and or published fail
• SL-211: Recordings are shown to the integrations even if the file does not exist

Enhancements

• SL-XX: Add rake task to sync cluster state (add/update/remove servers) from a YAML file #645

v1.2.0.1

Release notes - Scalelite - Version 1.2.0.1

Bug

• SL-215 Poller fails due to old Amazon-Linux Certificates Git ##688
• SL-214 scalelite-nginx fails to respond to old recordings

v1.1.8.1

Release notes - Scalelite - Version 1.1.8.1

Bug

• SL-215 Poller fails due to old Amazon-Linux Certificates Git ##688

v1.2.0.1-beta.1

Release notes - Scalelite - Version 1.2.0.1-beta.1

Bug

• hot-fix for restoring supporting for recordings created with a BBB server 2.0 and earlier.

v1.2

Release notes - Scalelite - Version 1.2

Epic

• SL-78 Implement protected recordings

Bug

• SL-206 CSRF token issue fix
• SL-202 Meta_analytics_url_checksum error #608
• SL-200 response to protected recordings is not backward compatible
• SL-199 getRecordings filter to prevent requests with no parameters is not correctly implemented

Improvement

• SL-212 guides for upgrading SL from 1.1 to 1.2-systemd

Notes

This release requires to run migrations. And despite a modification was made to the bin/start script to allow running migrations on start, if the api or imported recordings don't work correctly, it may be needed to run the migration directly.

docker exec -t scalelite-api bundle exec rake db:migrate

There are a few new environment variables:

RECORDING_PLAYBACK_FORMATS: Recording playback formats supported by Scalelite, defaults to presentation:video:podcast:notes:capture.

PROTECTED_RECORDINGS_ENABLED: Applies to the recording import process. If set to "true", then newly imported recordings will have protected links enabled. Default is "false".

PROTECTED_RECORDINGS_TOKEN_TIMEOUT: Protected recording link token timeout in minutes. This is the amount of time that the one-time-use link returned in getRecordings calls will be valid for. Defaults to 60 minutes (1 hour).

PROTECTED_RECORDINGS_TIMEOUT: Protected recordings resource access cookie timeout in minutes. This is the amount of time that a user will be granted access to view a recording for after clicking on the one-time-use link. Defaults to 360 minutes (6 hours).

Please see mode details about Protected Recordings

v1.1.8

Release notes - Scalelite - Version 1.1.8

Bug

• SL-206 CSRF token issue fix
• SL-203 SL-199 - getRecordings filter to prevent requests with no parameters is not correctly implemented
• SL-190 Meta_analytics_url_checksum error # 608

Improvement

• SL-209 Fix db:migrate task and auto-bootstrap DB in bin/start

v1.2-beta.3

Release: major 1, minor 2, beta 3

v1.1.8-beta.3

Release: major 1, minor 1, revision 8, beta 3

v1.2-beta.2

Release: major 1, minor 2, beta 2