-
Notifications
You must be signed in to change notification settings - Fork 640
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
add talk-recording container #2645
Conversation
no idea why the spellcheck crashes while building |
It fails because we now have some self-hosted github action runners that run very fast into rate limitations with docker hub. |
@Zoey2936 Thank you very much for this! Actually I was unfortunately not clear enough with this. I imagined to create a separate container for the recording server since based on @danxuliu it takes a lot of ressources to run. For smaller instances to still run the talk HPB and turnserver, I would split things up. Another solution would be to still deliver it with this one container and allowing to disable the recording server via environmental variable. WDYT? :) |
it seems like recording depends on signaling, thats the reason why I added it here, but an env sounds good |
Yes indeed so I would just limit the recording server to get chosen only if the talk hpb is enabled as well. WDYT about a separate container? Or do you think that having everything in one container would be the better way here? |
Actually since the recording server also needs many dependencies putting it into another container maybe makes it easier to maintain? |
This comment was marked as off-topic.
This comment was marked as off-topic.
then lets move it to its own container |
4a96539
to
dc18680
Compare
done, I think |
I've pushed talk v16.0.3 instead of .4 to check if the update workflow works and also to check if the config gets updated |
Thanks a lot Zoey! I'll have a look probably on monday! :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you very much for tackling this! :)
Some comments
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some comments
Signed-off-by: Zoey <zoey@z0ey.de>
Signed-off-by: Simon L <szaimen@e.mail.de> Signed-off-by: Zoey <zoey@z0ey.de>
Signed-off-by: Zoey <zoey@z0ey.de>
Signed-off-by: Zoey <zoey@z0ey.de>
Signed-off-by: Zoey <zoey@z0ey.de>
Signed-off-by: Zoey <zoey@z0ey.de>
Signed-off-by: Zoey <zoey@z0ey.de>
Signed-off-by: Zoey <zoey@z0ey.de>
Signed-off-by: Zoey <zoey@z0ey.de>
Signed-off-by: Zoey <zoey@z0ey.de>
Signed-off-by: Zoey <zoey@z0ey.de>
Signed-off-by: Zoey <zoey@z0ey.de>
Signed-off-by: Zoey <zoey@z0ey.de>
Signed-off-by: Zoey <zoey@z0ey.de>
Signed-off-by: Simon L <szaimen@e.mail.de>
Signed-off-by: Simon L <szaimen@e.mail.de>
Signed-off-by: Simon L <szaimen@e.mail.de> Signed-off-by: Simon L. <szaimen@e.mail.de>
For #2527
I've added recording.conf to the update script to see, when there are changes done to it, also backend.secret needs to be changed in the config and added to all other configs in aio
@szaimen If you want just add all other recording changes to this PR