Major backend update#386
Conversation
Add functionality for creating new stream profiles through the executable using specific flags
I have tested setting up a caddy instance on my own domain, and it seems to work somewhat. The only thing I have a little issues with was actually getting it to stream. Is this something that has worked for you on the latest main branch? |
Will start out loading .env if available, and then .env.development or .env.production, in that order. Whichever is found first is applied, and variables conflicting with .env will overwrite .env variables.
Make WhepHandler public and accessible for networktest. Add networktest flag
Yes, main branch is working fine. I will test again later with your latest changes. |
Use of .Load() does not overwrite already existing variables from .env, Overload does, and assures that despite what defaults has been set in .env, they are overwritten by the dev/prod .env file
This only applies when not set in .env files
|
@IIamaseconds does this break existing users at all? I noticed some env variables changed, maybe worth undoing? any users that break maybe will stop using broadcast box :( I’m all for breaking things that improve users experience though! |
I'm just an end user so I can't really assist with code, but I'm getting this as of the past few minutes. |
|
You would be right, I actually got so focus on people just pulling the image and not actually configuring it and persisting it while I was testing. |
|
@Tathagata-0 - Are you on the discord? Maybe I can have a quick chat with you and resolve this. :-) |
|
@IIamaseconds I am sorry, but I think you need to revert :( For every user that comes on GitHub we are gonna have 10x that break and decide they don't want to use Broadcast Box anymore. What do you think of reverting (just temporarily) and doing small changes/make sure users don't break? That's the only thing we can't compromise on |
|
I completely agree! Lets revert! And I will look into the settings being fixed! Sorry I didn't get to test that part thorough enough! I am going to replace the 'latest' so that people will pull the prechange version of the image! :-) |
|
Revert should be done now, and "latest" is back to previous version. Seems like it works here. |
|
Also, @Sean-Der - I think you are right that it is the .env files. |
No luck for me, but I was using https://b.siobud.com/api/whip before as I haven't able to figure out how to get it to work locally (in general). |
|
Sorry about that @Tathagata-0 b.siobud.com is be back now! also if you are interested would love to help you self host :) |
|
@IIamaseconds I don’t use We can’t break these settings. Can you please revert (because I deploy against I love all the stuff in the PR. I also believe it’s achievable with zero breakage right? |
|
@Sean-Der Awesome! As for self-hosting, that sounds great, I can visit the Discord when I have some time (assuming that's the best place to ask). |
4 participants
Massive rewrite of the backend.
Introduces new features as well
These can be created through the backend executable with flags '-createNewProfile -streamKey TheKey'
It is now possible to stream multiple audio tracks as well as multiple video tracks to the same stream.
When using public streaming keys where anyone can submit to the same streams, it will now create separate layers against the stream instead of sending all WHIP packets to the same receiving layer, causing image interpolation and audio issues
Vite now has a proxy which helps when using a self-signed certificate for development locally
Other minor things has been added as well, and a lot of changes to how WHIP and WHEP works.
This will require more testing, so if anyone is able to give it a look through in the coming time to verify that things looks and operates correctly, it would be appreciated. I have tested myself and will continue to do so to catch small issues and fix them before merging.