Icecast still exists? Blast from the past. Does it work reliably yet?
I've had years of uptime with icecast at home.
TinyIce: Single-binary Icecast2-compatible server (auto-HTTPS, multi-tenant)
21–30 of 35 posts
Re: TinyIce: Single-binary Icecast2-compatible server (auto-HTTPS, multi-tenant)
#22Thanks for sharing! Would love to see configurable ACME settings for use in a homelab where I'm already running my own ACME CA.
Re: TinyIce: Single-binary Icecast2-compatible server (auto-HTTPS, multi-tenant)
#23Thanks for sharing! Would love to see configurable ACME settings for use in a homelab where I'm already running my own ACME CA.
thank you for trying. I have added it in the latest release.
Re: TinyIce: Single-binary Icecast2-compatible server (auto-HTTPS, multi-tenant)
#24Dose it work behind a reverse proxy such as nginx? Especially for the m3u8 files?
That should work! :) Just added m3u/m3u8 support.
Re: TinyIce: Single-binary Icecast2-compatible server (auto-HTTPS, multi-tenant)
#25I've just added better docs, the CI/CD pipeline is now releasing binaries for all major platforms and custom ACME URLs are supported.
Re: TinyIce: Single-binary Icecast2-compatible server (auto-HTTPS, multi-tenant)
#26The HTTPS is still a problem for some streaming music sites. e.g. streamingsoundtracks.com runs HTTP.
Running my own icecast2 server, I recently ran into a problem[1] where TLS connections don't shut down properly. It's actually a problem with the libshout client library's poor TLS support. I posted a patch to that issue, but it's hard to tell if there's anyone still looking at issues or actively developing the project over there. The last update to libshout was 3 years ago, and it was just a documentation cleanup. 1…
This should be working in tinyice without issues. Feel free to test it and if the problem is also present, I will fix it.
Re: TinyIce: Single-binary Icecast2-compatible server (auto-HTTPS, multi-tenant)
#27I 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.
What was frustrating Icecast?
XML-based big configuration, confusing for new users. No "run a single binary" and that's it :)
Re: TinyIce: Single-binary Icecast2-compatible server (auto-HTTPS, multi-tenant)
#28Here is a little writeup on medium.com: https://syso42.medium.com/tinyice-how-i-created-a-single-bin...
Re: TinyIce: Single-binary Icecast2-compatible server (auto-HTTPS, multi-tenant)
#29I 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.
Thank you so much. I just added a lot of new features and polished some old ones now.
Re: TinyIce: Single-binary Icecast2-compatible server (auto-HTTPS, multi-tenant)
#30The 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?
It doesn’t “just” work, I just implemented a streaming radio client and the http streams were a nightmare