Open leandromoreira opened 1 year ago
Thanks @leandromoreira, well done!
When we created the sample all-in-one setup few weeks ago, we considered providing a docker image. The main reason we didn't go with this approach, was the transcoding part. I wanted to use the existing transcoder dockerfile, since getting the dependencies right for ffmpeg may not be trivial. And, I wanted to run the transcoding dockers on-demand - for every incoming stream that needs transcoding. If the controller also runs in docker, not sure there's a reasonable way to accomplish this... if you have some ideas about this, please share :) Either way, I'm ok with adding a sample docker compose + dockerfile for the all-in-one setup.
Providing the sample controller in Golang is also a good idea. When we started this project 3+ years ago, I wasn't familiar with Golang... so PHP was a more natural decision for me :) But I agree Golang is a better choice moving forward.
@erankor thank you for sharing your team's work :) I'm going to try to port the transcoder part as well before creating a PR right here.
This is quite excellent. I will contribute as well. Additionally, one can deploy this with Xilinx FPGA-driven ffmpeg instances.
Hi team,
Thanks for sharing this surprising set of projects. I built a docker image and a docker-compose to provide a complete docker all-in-one usage example.
It's missing the
transcoding
part plus some TODOS AND for sure many other things I have missed, but it's working!I'd like to know your thoughts (and any suggestions)! I also was wondering if you'd like to have this stand-alone docker usage example in here (maybe in a folder
docker_example
), or maybe it should keep living in an external repo.