I'm not either š
Note, no clue if the docker stuff works. IDK a lot about docker. I mean I do not just enough to be dangerous.
Discussion
I tried the docker method this evening. The website is working but RTMP isn't. netstat inside the container says nothing is listening on 1935... I wasn't sure if your listing ffmpeg on the release page as a requirement meant we needed to install it separately, so I added it to the container, but still no working RTMP (though the logs say it is? š¤·āāļø (see below)). I'll take a fresh look tomorrow.
2025/09/08 05:06:09 š¬ Starting RTMP server on port 1935...
2025/09/08 05:06:09 š¬ RTMP server (FFmpeg-based) starting on port 1935
2025/09/08 05:06:09 š„ Starting RTMP server for stream: default
2025/09/08 05:06:09 ā RTMP server listening on rtmp://0.0.0.0:1935/live
try changing it from 0.0.0.0 to your machines ip and then try to connect to it that way.
I should have included ffmpeg as a dependency for the container and I'm not sure if I did. So I'll check on that.
Yup, I came to the same conclusion. Added the following to Dockerfile-prerelease and the rest worked:
# Install build dependencies for FFmpeg
RUN apk add --no-cache --virtual .build-deps \
build-base coreutils git nasm pkgconf yasm \
rtmpdump-dev openssl-dev x264-dev x265-dev freetype-dev libvorbis-dev opus-dev libvpx-dev lame-dev libtheora-dev xvidcore-dev \
fontconfig-dev fribidi-dev libass-dev
# Clone and build FFmpeg with librtmp disabled
RUN git clone --depth 1 https://git.ffmpeg.org/ffmpeg.git /tmp/ffmpeg && \
cd /tmp/ffmpeg && \
./configure \
--enable-gpl \
--enable-nonfree \
--enable-openssl \
--enable-libx264 \
--enable-libx265 \
--enable-libfreetype \
--enable-libvorbis \
--enable-libopus \
--enable-libvpx \
--enable-libmp3lame \
--enable-libtheora \
--enable-libxvid \
--enable-libfontconfig \
--enable-libfribidi \
--enable-libass \
--disable-debug \
--disable-doc \
--disable-ffplay && \
make -j$(nproc) && \
make install && \
cd /tmp && \
rm -rf /tmp/ffmpeg