search for: git_workflow

...and ABI may still change slightly before release! I would love to get some input and bug reports. I believe this is a huge step forward for libshout (also those internals we changed that will also help us to do other stuff that is on our TODO list). Getting libshout: https://wiki.xiph.org/Icecast/Git_workflow Ticket: https://trac.xiph.org/ticket/2152 -- Philipp. (Rah of PH2) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 490 bytes Desc: This is a digitally signed message part Url : http://lists.xiph.org/pipermail...

...to the user. All security fixes are also communicated on their own. Got curious? To get the most recent updates you sadly need to install Icecast from source on your own. Please see: * https://wiki.xiph.org/Icecast_Server/Getting_Started * https://wiki.xiph.org/Icecast_Server/Git_workflow With best regards, -- Philipp Schafft (CEO/Geschäftsführer) Telephon: +49.3535 490 17 92 Löwenfelsen UG (haftungsbeschränkt) Registration number: Bickinger Straße 21 HRB 12308 CB 04916 Herzberg (Elster) VATIN/USt-ID: Germany...

...ook at that link. I think it is better than most but it has some oddities. I would generally recommend to have a look at: https://wiki.xiph.org/Icecast_Server/Installing_latest_version_(official_Xiph_repositories) If you *really* want to build your own Icecast: https://wiki.xiph.org/Icecast_Server/Git_workflow However those two are "just" the install part, not the setup part. > I'm using a valid certificate from letsencrypt on a Ubuntu 18 server hosted > by AWS. Icecast recognizes this without issue. I wouldn't recommend AWS with Icecast as several of my clients had problems w...

...ide every package repository: > > http://download.opensuse.org/repositories/multimedia:/xiph:/beta/Debian_9.0/ > > It's actually identical for all Debian and Ubuntu releases. > > > The other option is to build from source: > > https://wiki.xiph.org/Icecast_Server/Git_workflow > > so basically: > > git clone --recursive https://git.xiph.org/icecast-server.git > cd icecast-server > ./autogen.sh > ./configure > make > > > Importantly: omit the "make install" and just manually replace the > binary - and if necessary the web...

Hi, When installing Icecast2 (stable) on Debian9 using ATP packet manager, we need to go into /etc/default/icecast and enable the init.d script with ENABLE=true if we want to run Icecast as a service. I?ve been playing with icecast 2.5 beta installed from source and obviously this means things are located in different places. I would like to know if it is also possible to run this version as a

...port to Icecast. Currently there is no public module that uses it, yet. Yet it will allow future development of optional components. Got curious? Feel free to try it yourself: * https://wiki.xiph.org/Icecast_Server/Getting_Started * https://wiki.xiph.org/Icecast_Server/Git_workflow Also feel free to join us on IRC at #icecast on Freenode. For more details see: https://icecast.org/contact/#contact-info With best regards, -- Philipp Schafft (CEO/Geschäftsführer) Telephon: +49.3535 490 17 92 Löwenfelsen UG (haftungsbeschränkt) Registration number: Bickinger Straße 21...

Hi. I configured icecast to serve a stream over ssl and it plays nice in Chrome and VLC. But on plain http I get *connection reset*. This stream's url is the same for many years now, and it is included in many radio directories, TuneIn and other apps. I can't change it or break it. Is there a way to have a stream that servs the content over ssl and plain http in the same time, depending

Hi team, Please accent my apologies if this is NOT the place/distro list to be raising this. I had major dramas with the standard forum - registration and decided this may be a better route. My current instance icecast server has been built with --with-curl --with-openssl options as outlined within this post: https://weekly-geekly.github.io/articles/350236/index.html and the build version is

Hello, I didn't want to have to choose between Icecast running on port 80 and all my Apache virtual hosts, running also on port 80, on my sole external IP address. I didn't want either to open port 8000 on my firewall because I wanted all users being able to reach Icecast even the ones behind enterprise firewalls. So I managed to run Apache 2.2 listening on port 80 and Icecast 2.3.2