Ocyss/srs-auth / .agents/skills/internal-docs-for-srs
internal-docs-for-srs
FlaggedRoute SRS and Oryx tasks to the smallest relevant set of trusted project documentation and maintain the project documentation bundled with this skill. Use whenever support or development work requires locating, choosing, reading, creating, updating, or reviewing SRS documentation, or whenever Oryx work requires project documentation for deployment, streaming, authentication, recording to local or S3-compatible storage, restreaming, virtual live, camera, transcoding, HTTPS, APIs, callbacks, AI features, or development. Includes the C++ media server documentation, Oryx project documentation, website pages, changelog, executable API examples, and next-generation Go server and performance documentation.
references/proxy/proxy-usage.md
View on GitHub# How to Run and Test the Project
When running the project for testing or development, you should:
1. Build and start the proxy server
2. Start SRS origin server
3. Verify SRS registration with proxy
4. Publish a test stream using FFmpeg
5. Verify the stream is working using ffprobe
## Step 1: Build and Start Proxy Server
```bash
make && env PROXY_RTMP_SERVER=1935 PROXY_HTTP_SERVER=8080 \
PROXY_HTTP_API=1985 PROXY_WEBRTC_SERVER=8000 PROXY_SRT_SERVER=10080 \
PROXY_SYSTEM_API=12025 PROXY_LOAD_BALANCER_TYPE=memory ./bin/srs-proxy
```
The proxy server should start and listen on the configured ports.
## Step 2: Start SRS Origin Server
In a new terminal, start the SRS origin server. You may need to increase the file descriptor limit and use bash explicitly:
```bash
ulimit -n 10000 && bash -c "cd ~/git/srs/trunk && ./objs/srs -c conf/origin1-for-proxy.conf"
```
The SRS origin server should start and be ready to receive and serve streams. Check the console output for startup messages.
## Step 3: Verify SRS Registration
Check the proxy logs to confirm SRS has registered itself with the proxy:
The proxy logs are printed to the console where you started the proxy server. Check the terminal running the proxy for messages indicating:
- "Register SRS media server" messages when SRS registers itself with the proxy
The SRS origin server should automatically register itself with the proxy when it starts. Look for successful registration messages in proxy console outputs.
## Step 4: Publish a Test Stream
In a new terminal, publish a test stream using FFmpeg:
```bash
ffmpeg -stream_loop -1 -re -i ~/git/srs/trunk/doc/source.flv -c copy -f flv rtmp://localhost/live/livestream
```
> Note: `-stream_loop -1` makes FFmpeg loop the input file infinitely, ensuring the stream doesn't quit after the file ends.
## Step 5: Verify Stream with ffprobe
In another terminal, use ffprobe to verify the stream is working:
**Test RTMP stream:**
```bash
ffprobe rtmp://localhost/live/livestream
```
**Test HTTP-FLV stream:**
```bash
ffprobe http://localhost:8080/live/livestream.flv
```
Both commands should successfully detect the stream and display video/audio codec information. If ffprobe shows stream details without errors, the proxy is working correctly.
## Code Conventions
## Factory Functions
- Factory functions should use explicit interface names: `NewProxyBootstrap()`, `NewMemoryLoadBalancer()`, etc.
- **Do not** use generic `New()` function names
- This improves code clarity and makes the constructed type explicit at the call site
- Example:
```go
// Good
bs := bootstrap.NewProxyBootstrap()
// Avoid
bs := bootstrap.New()
```
## Global Variables
- Avoid global variables for service instances
- This improves testability and makes code flow explicit
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |