TinyIce: Single-binary Icecast2-compatible server (auto-HTTPS, multi-tenant)
1–10 of 35 posts
Re: TinyIce: Single-binary Icecast2-compatible server (auto-HTTPS, multi-tenant)
#2Re: TinyIce: Single-binary Icecast2-compatible server (auto-HTTPS, multi-tenant)
#3Re: TinyIce: Single-binary Icecast2-compatible server (auto-HTTPS, multi-tenant)
#4Re: TinyIce: Single-binary Icecast2-compatible server (auto-HTTPS, multi-tenant)
#5I 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.
I think it's really neat how you managed to include ACME, a nice UI and even the Prometheus metrics.
Re: TinyIce: Single-binary Icecast2-compatible server (auto-HTTPS, multi-tenant)
#6The HTTPS is still a problem for some streaming music sites. e.g. streamingsoundtracks.com runs HTTP.
Why would you military grade encrypt radio service or static site anyway?
Re: TinyIce: Single-binary Icecast2-compatible server (auto-HTTPS, multi-tenant)
#7Re: TinyIce: Single-binary Icecast2-compatible server (auto-HTTPS, multi-tenant)
#8The 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?
Re: TinyIce: Single-binary Icecast2-compatible server (auto-HTTPS, multi-tenant)
#9The 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?