-
Notifications
You must be signed in to change notification settings - Fork 44
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
Only one streaming key for each course #1242
Closed
Mjaethers
wants to merge
31
commits into
TUM-Dev:dev
from
Mjaethers:124-require-only-one-streaming-key-for-each-course
Closed
Only one streaming key for each course #1242
Mjaethers
wants to merge
31
commits into
TUM-Dev:dev
from
Mjaethers:124-require-only-one-streaming-key-for-each-course
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This reverts commit 8beb8dd.
Revert "stream keys are read from course if defined" This reverts commit 8beb8dd. Added version tag to website footer (TUM-Dev#1238) * Added version tag to website footer * Changed layout stream keys are read from course if defined
Apologies regarding the state of the git history, I learned my lesson about syncing forks. |
Mjaethers
deleted the
124-require-only-one-streaming-key-for-each-course
branch
January 31, 2024 11:48
Mjaethers
restored the
124-require-only-one-streaming-key-for-each-course
branch
January 31, 2024 11:49
Mjaethers
deleted the
124-require-only-one-streaming-key-for-each-course
branch
January 31, 2024 11:54
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation and Context
Closes #124
Currently, every time a lecturer starts a new self-stream, they have to go into their streaming software and change the stream server and key. This is a bit cumbersome as most lecturers only need to stream to one course, and therefore the credentials should be course-specific, instead of stream-specific.
Description
Each course now has it's own stream key, which is generated when the course is created. Every time a new stream is created, it's stream key will default to the course stream key.
The stream key of a course can be regenerated in the course -> settings tab. This might be used if the stream key is leaked, or to re-sync all the stream keys should they have been changed individually.
The stream key of a stream can be regenerated in the Edit Lecture tab on the course page, this might be used for hosting concurrent streams of a course. Here the stream key can also be restored to the course stream key.
Since the worker can no longer identify streams by their key, it now identifies a stream by key and time. This will cause problems if stream times overlap within 30 minutes.
Steps for Testing
Prerequisites:
Screenshots
Changing the key of a specific stream
Changing the key of all stream in course