Skip to content

Fix profile README: librtmp2-server now integrates the librtmp2 crate#2

Merged
AlexanderWagnerDev merged 1 commit into
mainfrom
claude/bug-search-review-roq322
Jul 2, 2026
Merged

Fix profile README: librtmp2-server now integrates the librtmp2 crate#2
AlexanderWagnerDev merged 1 commit into
mainfrom
claude/bug-search-review-roq322

Conversation

@AlexanderWagnerDev

@AlexanderWagnerDev AlexanderWagnerDev commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

Summary

  • The org profile README documented the RTMP/E-RTMP listener in librtmp2-server as not yet wired up ("blocked on librtmp2 crate integration"). That's stale: librtmp2-server's Cargo.toml depends directly on the librtmp2 crate, and src/server.rs already uses librtmp2::server::Server / librtmp2::types::ServerConfig to drive its listener.
  • Updated the architecture note, feature list, architecture diagram, roadmap checklist, and use-case table to describe the integration as complete rather than in-progress.

Test plan

  • Verified the claim directly against librtmp2-server's Cargo.toml (librtmp2 = { git = ... } dependency) and src/server.rs (imports and uses librtmp2::server::Server)
  • N/A — documentation-only change, no build/tests to run

Generated by Claude Code

Summary by CodeRabbit

  • Documentation
    • Updated the project README to reflect that RTMP/RTMPS listener support is now live and powered by the embedded librtmp2 crate.
    • Revised the architecture overview, diagram, quick start steps, and use-case descriptions to match current behavior.
    • Marked the relevant roadmap items as completed instead of pending.

The RTMP/E-RTMP listener was previously documented as pending, but
librtmp2-server's src/server.rs already wires in librtmp2::server::Server
and Cargo.toml depends on the librtmp2 crate directly. Update the
architecture diagram, feature list, roadmap, and use-case table to reflect
the completed integration instead of describing it as in-progress.
Copilot AI review requested due to automatic review settings July 2, 2026 21:50
@coderabbitai

coderabbitai Bot commented Jul 2, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 73c46ef7-486d-4779-888c-8261c251f6eb

📥 Commits

Reviewing files that changed from the base of the PR and between ad7ee7a and 22baee1.

📒 Files selected for processing (1)
  • profile/README.md

📝 Walkthrough

Walkthrough

Documentation-only update to profile/README.md reflecting that librtmp2 is now integrated into librtmp2-server for RTMP/RTMPS listening. Text in dependency notes, architecture description/diagram, quick start, use cases, and roadmap checkboxes were revised from "pending"/"not yet" to completed status.

Changes

README librtmp2 Integration Status Update

Layer / File(s) Summary
Integration status updates
profile/README.md
Dependency notes, architecture narrative and diagram, quick start text, use case description, and roadmap checkboxes updated to state librtmp2 is now embedded/wired into librtmp2-server for RTMP/RTMPS listening, replacing prior "in progress"/"not yet" language.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Possibly related PRs

  • OpenRTMP/.github#1: Both PRs modify profile/README.md to adjust the stated architecture/wiring status between librtmp2 and librtmp2-server.
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly matches the README-only update and correctly states the main change: librtmp2-server now integrates librtmp2.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch claude/bug-search-review-roq322

Comment @coderabbitai help to get the list of available commands.

@AlexanderWagnerDev AlexanderWagnerDev merged commit 3f0a6b9 into main Jul 2, 2026
1 of 2 checks passed
@AlexanderWagnerDev AlexanderWagnerDev deleted the claude/bug-search-review-roq322 branch July 2, 2026 21:51

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the organization profile README to reflect that librtmp2-server now integrates the librtmp2 crate (rather than describing it as blocked/in-progress), and adjusts the architecture description/diagram and roadmap accordingly.

Changes:

  • Updates multiple references from “pending integration” to “integration complete” for librtmp2-serverlibrtmp2.
  • Refreshes the architecture note/diagram and use-case guidance to match the new state.
  • Marks the relevant roadmap items as completed.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread profile/README.md
- **[.github](https://github.com/OpenRTMP/.github)** — Organization documentation and CI/CD

> **Note:** `librtmp2` and `librtmp2-server` are both Rust today, but they are separate codebases — `librtmp2-server` does not yet depend on the `librtmp2` crate for its RTMP listener. See [Architecture](#architecture) below.
> **Note:** `librtmp2` and `librtmp2-server` are both Rust today, and separate codebases — `librtmp2-server` depends on the `librtmp2` crate to drive its RTMP/RTMPS listener. See [Architecture](#architecture) below.
Comment thread profile/README.md
## Architecture

`librtmp2` and `librtmp2-server` are both Rust, but independent codebases today — the server does not yet depend on the `librtmp2` crate for its RTMP listener.
`librtmp2` and `librtmp2-server` are both Rust, independent codebases — `librtmp2-server` depends on the `librtmp2` crate to drive its RTMP/RTMPS listener.
Comment thread profile/README.md
```

See [librtmp2-server README](https://github.com/OpenRTMP/librtmp2-server#build) for configuration and deployment. Note: RTMP ingest is not yet live — see the Architecture section above.
See [librtmp2-server README](https://github.com/OpenRTMP/librtmp2-server#build) for configuration and deployment. RTMP/RTMPS ingest runs via the embedded `librtmp2` crate — see the Architecture section above.
Comment thread profile/README.md
|----------|----------|
| **OBS/FFmpeg Plugin** | Use `librtmp2` (Rust, FFI-compatible) to add RTMP ingest support from any language |
| **Private RTMP Relay** | Build on `librtmp2`; `librtmp2-server` is not yet protocol-capable |
| **Private RTMP Relay** | Build on `librtmp2` directly, or run `librtmp2-server`, which embeds it |
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants