Comment on Personal radio station
rastacalavera@lemmy.world 11 hours ago
Azuracast on its head is over kill but will work and give you a nice webgui. If you run behind a vpn like Tailscale, nebula,etc just add the other person to it and no password is needed because your stream and service isn’t publicly available. Get your radio stream url and put it in VLC on mobile or use the web.
Technoworcester@feddit.uk 10 hours ago
Thankyou. Will have a look and a play. Overkill isn’t a bad thing for future proofing.
Psythik@lemmy.world 1 hour ago
If you don’t feel llke spending money just run a SHOUTcast server on your home PC/homelab/personal server, plus a small web server to serve as the front-end, and that way you can avoid paying the monthly fee for AsuraCast entirely.
cideyav138@lemmy.ml 4 hours ago
Just a heads up, their example Docker compose comes with a support for 50 radio stations (with 50+ ports mapped), and it isn’t meant to sit behind a reverse proxy. Below is a simplified Docker compose that I made to run a single radio station.
My nginx routes traffic to port 4580 using the subdomain I assigned for my station, and LetsEncrypt handles SSL. I use SWAG to manage all of that.
I can’t remember why, but
AZURACAST_STATION_PORTS: “8000,8005,8006”is in fact required for a single station. The Azuracast admin portal has an option to consolidate the public player and admin portal behind a single domain, soradio.example.comhits the public player andradio.example.com/loginhits the admin login.It’s nowhere near the level of pain you have to go through to run Matrix with chat bridges on Docker, but getting all of that right and simplified was more work than I wanted it to be. Hope this helps!