Closed gorfreed closed 2 years ago
Thanks for bringing this to my attention. There a few updates required for all containers which I should have uploaded this week.
I don't fully want to rule out my incompetence though, but when following the install instructions strictly, the above described result will occur. Looking forward to the update!
Still no update. Shoot, I guess I was too late for this one. It would have been the perfect solution... If anyone reads this and knows an alternative, please let me know!
Hi @gorfreed! Sorry I've been a bit sidetracked with the log4j vulnerabilty that came out. Can you try the major-fixes
branch. Everything should run, expect I'm still trying to fix an issue where the track data is not displayed on the web radio player.
This has now been merged to the main branch. Liquidsoap is pinned to v1.4.4 while I figure out why the metadata doesn't work on v2.0.0.
Hello!
Bottle Radio is exactly what I have been looking for after going down the same road with Azuracast than you did - I really appreciate your description :) Unfortunately it took me over a year to find this repo, and it seems there are some issues I am unable to solve. They are all related to the installation of the components used failing. I am not a developer but I am running my fair share of docker-deployed services, so I assume this compose script requires a little more knowledge than described in your installation guide. Or it is simply outdated.
This has been verified on three of my VPS (2x 20.04, 1x 18. 04). By just following your install instructions, docker-compose up fails with:
I have researched this error and it seems to be quite common when compiling nodejs projects (https://github.com/webpack/webpack/issues/14532). So I tried putting the "--openssl-legacy-provider" into the package.json react script build reference, and it actually worked - only to be stopped when installing Mopidy:
So yeah, it seems to be pretty broken atm. Or I am missing something. Please help me out!