I built TinyIce as a vibing side project to spin up an Icecast2-compatible server in seconds, because I was frustrated with IceCast. One static Go binary, embedded assets, auto-generated creds on first run, built-in ACME (Let’s Encrypt), relays, multi-tenant admins, Prometheus metrics, and a modern web UI.
TinyIce: Single-binary Icecast2-compatible server (auto-HTTPS, multi-tenant)
11–20 of 35 posts
Re: TinyIce: Single-binary Icecast2-compatible server (auto-HTTPS, multi-tenant)
#12I built TinyIce as a vibing side project to spin up an Icecast2-compatible server in seconds, because I was frustrated with IceCast. One static Go binary, embedded assets, auto-generated creds on first run, built-in ACME (Let’s Encrypt), relays, multi-tenant admins, Prometheus metrics, and a modern web UI.
It's a very nice project. Me and some friends toyed with the idea of running our own IceCast server, as a way to introducing new music to each other. We eventually gave up, exactly due to frustrations with setting up and running IceCast. I think it's really neat how you managed to include ACME, a nice UI and even the Prometheus metrics.
Get onto Music League for introducing new music to each other.
Someone setup a league at work, and it's been one of the best (albeit unintentional) team bonding exercises I've ever come across (I've not come across many). So much so that three people who have left the company still participate in the league.
It unfortunately it's linked to and requires the use of Spotify, for those who are ideologically opposed (which also means I can't submit King Gizzard and the Lizard Wizard songs anymore).
Re: TinyIce: Single-binary Icecast2-compatible server (auto-HTTPS, multi-tenant)
#13The HTTPS is still a problem for some streaming music sites. e.g. streamingsoundtracks.com runs HTTP.
why this is a problem? Streaming over Http just works - even on clients from 1999 like Winamp. Why would you military grade encrypt radio service or static site anyway?
TLS doesn’t just offer confidentiality, it also offers integrity.
Re: TinyIce: Single-binary Icecast2-compatible server (auto-HTTPS, multi-tenant)
#14Earlier quoted context omitted.
why this is a problem? Streaming over Http just works - even on clients from 1999 like Winamp. Why would you military grade encrypt radio service or static site anyway?
Because some browsers get annoyed and put up lots of alerts if they can't make a https connection
Re: TinyIce: Single-binary Icecast2-compatible server (auto-HTTPS, multi-tenant)
#15Earlier quoted context omitted.
why this is a problem? Streaming over Http just works - even on clients from 1999 like Winamp. Why would you military grade encrypt radio service or static site anyway?
To keep your ISP from slipping ads into the audio stream? To keep RIAA from finding out what you're streaming and suing you into oblivion?
Re: TinyIce: Single-binary Icecast2-compatible server (auto-HTTPS, multi-tenant)
#16Re: TinyIce: Single-binary Icecast2-compatible server (auto-HTTPS, multi-tenant)
#17Re: TinyIce: Single-binary Icecast2-compatible server (auto-HTTPS, multi-tenant)
#18Re: TinyIce: Single-binary Icecast2-compatible server (auto-HTTPS, multi-tenant)
#19[flagged]
Re: TinyIce: Single-binary Icecast2-compatible server (auto-HTTPS, multi-tenant)
#20The HTTPS is still a problem for some streaming music sites. e.g. streamingsoundtracks.com runs HTTP.
1: https://gitlab.xiph.org/xiph/icecast-libshout/-/issues/2337