feat: add Oryx (SRS) media streaming template#1027
Open
Siumauricio wants to merge 1 commit into
Open
Conversation
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
built with Refined Cloudflare Pages Action⚡ Cloudflare Pages Deployment
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a template for Oryx (formerly SRS Stack), an all-in-one open-source video streaming server built on SRS, with a web console for managing streams, recording, forwarding, transcoding and virtual live streaming.
ossrs/oryx:5.15.20(latest stable release on Docker Hub)oryx-datavolume (/data)instructions.mdcovers the first-login password setup and the RTMP/SRT/WebRTC publish URLsPort decision
RTMP, SRT and WebRTC are not HTTP protocols, so Traefik cannot route them through the domain. Following the precedent set by the
poste.iotemplate (which publishes its mail ports the same way), the streaming ports are published directly on the host, with a comment in the compose file explaining why:1935:1935— RTMP ingest/playback (TCP)8000:8000/udp— WebRTC media transport (UDP)10080:10080/udp— SRT ingest/playback (UDP)Users publish streams against the server IP on these ports; HLS/HTTP-FLV playback and the console go through the HTTPS domain. This is documented in
instructions.md.Test evidence
Deployed on a Dokploy instance from this exact blueprint:
done(123s), container runningGET /via the assigned domain → HTTP 200,<title>Oryx</title>(management console)GET /terraform/v1/mgmt/init→{"code":0,"data":{"init":false}}(first-run admin setup ready)nc -vz SERVER_IP 1935→ connection succeeded (RTMP reachable)node build-scripts/generate-meta.js --check→ 481 templates validatedCloses #300
🤖 Generated with Claude Code