Ability to configure, and/or disable internal Icecast service

[MNTLe-DMGD]

Once configuration, media import etc is complete, going live to listeners would likely require an external Icecast/Shoutcast server. It would be handy to have a way to either reconfigure Icecast, or even disable it completely.

Using an external Icecast/Shoutcast server for production purposes would ease server load (minimal I guess), and decrease bandwidth usage.

For dev; setup and local network listening purposes, the internal Icecast server is perfect, but moving to production may require more bandwidth.

This is not an error or issue, just a feature request for your spare time.

Thanks again for your great work!

[rallep71]

hello, it is now possible to connect to an external icecast server.

Personally I had never run libretime or airtime locally, always on a vps.

It would be interesting to put libretime behind a reverse proxy, for example nginx + https + letsencrypt, but unfortunately it fails again and again because of mixed content in libretime, even with the dockerfile.

[MNTLe-DMGD]

for example nginx + https + letsencrypt,

@rallep71 - Your request, might be a separate issue, and may need a separate bug/feature request logged.

Connecting to an external Icecast server is indeed possible. The feature request I've made is to have the ability to edit and/or disable the Icecast server within the docker.

[kessibi]

It would be handy to have a way to either reconfigure Icecast, or even disable it completely.

For this, I propose putting the icecast config files (which sit in /etc/icecast2 I believe) in the volume so they can be accessible on the host machine.

The feature request I've made is to have the ability to edit and/or disable the Icecast server within the docker.

I'm not sure this is possible easily as libretime installs a lot of things when running the installation script. It needs icecast at this point and probably elsewhere to run perfectly. I'll keep the issue open for debate though as I might be completely wrong and need insight on the issue.

@rallep71 libretime gives the ability to change the default icecast2 config in Settings > Streams. I believe you can point to another icecast server (external) but I have never done it myself.

As for your other issue, please open a new issue ticket with what you're exactly trying to do with nginx, letsencrypt, ... Having an article in the wiki about Libretime accessible from HTTPS is on my TODO list and your issue could be the entrypoint.

[MNTLe-DMGD]

I'm not sure this is possible easily as libretime installs a lot of things when running the installation script. It needs icecast at this point and probably elsewhere to run perfectly

Ahh! That makes sense. My assumption was that the packages were pre-installed, with the configuration happening after the fact. If this cant be done, no problem. The resources used by Icecast are fairly insignificant. I just thought it might be nice to have the ability to kill it off if it's not being used.

I think that there is a config file /etc/default/icecast2 which has a variable ENABLE=true. I think you can change it to ENABLE=false and it will prevent Icecast from starting. I don't know if that helps?

I propose putting the icecast config files (which sit in /etc/icecast2 I believe) in the volume so they can be accessible on the host machine.

I think the path is correct. Sounds like a plan.

[rallep71]

@kessibi normal you don't need a locally installed icecast server, /master and /show sources as well as the stream output controls liquirsoap alone in libretime. You only have to configure an external icecast server, the file is the icecast.xml, depending on the file in /etc/icecast2/... i had made some very complex videos on my youtube channel a while ago, icecast + liquitsoup nginx-rtmp and so on...

[rallep71]

@kessibi
"As for your other issue, please open a new issue ticket with what you're exactly trying to do with nginx, letsencrypt, ... Having an article in the wiki about Libretime accessible from HTTPS is on my TODO list and your issue could be the entrypoint."

for this i will create a detailed clipboard, dedicated server, docker-libretime, docker-icecast, nginx proxy and loadbalancer with letsencrypt, and so on, i need a little time for this

[Aphris-Karu]

Libretime does not work behind a reverse proxy that handles https. It is a known issue and one I ran into trying to get haproxy to handle the connection.