🚀 Overview

Elderberry is a production-ready, self-hosted real-time meeting script that combines
Node.js (signaling/back end), React (front end) and Mediasoup (SFU media server) to deliver
low-latency audio, video, and screen sharing straight from the browser using the native getUserMedia API. It is designed
for teams, classrooms, community platforms, and SaaS founders who want to own their meeting stack instead of relying on third-party
services. :contentReference[oaicite:1]{index=1}

Users can create or join rooms, enable mic/camera, share their screen, and chat — all over a single-page React interface. Because it
uses Mediasoup’s SFU pattern, it’s more scalable than pure peer-to-peer WebRTC for multi-party calls. :contentReference[oaicite:2]{index=2}

✨ Key Features

• 📡 Real-time A/V meetings – capture audio and video in the browser via navigator.mediaDevices.getUserMedia() and stream to the room. :contentReference[oaicite:3]{index=3}
• 🖥️ Screen sharing – share your screen or tab for demos, classes, or remote support. :contentReference[oaicite:4]{index=4}
• 🧠 Mediasoup SFU – centralized media server for multi-party calls that’s more bandwidth-efficient than mesh WebRTC. :contentReference[oaicite:5]{index=5}
• ⚛️ React front end – modern SPA UI, room list, participant tiles, mute/unmute, cam on/off. :contentReference[oaicite:6]{index=6}
• 💬 In-room chat – text chat alongside audio/video sessions.
• 🔐 Room control – host/moderator role can admit, mute, or end session (depending on version). :contentReference[oaicite:7]{index=7}
• 🌍 Self-hosted / on-prem – run on your own VPS or cloud so media stays under your control.
• 📱 Responsive UI – works on desktop and modern mobile browsers that support WebRTC.
• 🧪 Developer-friendly – code is split into client (React) and server (Node.js + Mediasoup) for easy extension. :contentReference[oaicite:8]{index=8}

⚙️ Technical Stack

• Back end: Node.js (Express/WebSocket for signaling) + Mediasoup v3 SFU. :contentReference[oaicite:9]{index=9}
• Front end: React SPA (Axios/WebSocket client, hooks-based components). :contentReference[oaicite:10]{index=10}
• RTC: WebRTC using getUserMedia, RTCPeerConnection, and Mediasoup transports.
• Runtime requirements: Node.js 16+ (or version specified in docs), npm/yarn, SSL/HTTPS for production WebRTC. :contentReference[oaicite:11]{index=11}
• Server: Linux VPS or Docker-based deployment; public IP required for mediasoup; STUN/TURN recommended. :contentReference[oaicite:12]{index=12}

E-E-A-T (Expertise): This follows the same architecture shown in Mediasoup official examples (router → transport → producer/consumer) and common React+Node boilerplates for signaling. :contentReference[oaicite:13]{index=13}

🧩 Installation Guide

1. 📦 Download / clone the Elderberry package (client + server). :contentReference[oaicite:14]{index=14}
2. 🧪 Install back end: go into /server → run npm install → configure .env (ports, public IP, mediasoup settings, TURN if any).
3. ⚛️ Install front end: go into /client → run npm install / yarn → set API/WS URL to your server.
4. 🛰️ Run server: npm run start or pm2 start for production.
5. 🖥️ Build React: npm run build and serve the static build (Nginx, Vite preview, or Node static).
6. 🔐 Enable HTTPS: configure SSL (e.g. Let’s Encrypt) because many browsers require secure context for screen sharing.
7. ✅ Test: open two different browsers/devices, join the same room, verify audio/video/screen sharing.

Tip: for production, run the Node.js server behind Nginx reverse proxy and tune Mediasoup worker numWorkers and rtpUdpPortRange for your VPS size.

📦 Deliverables

• 🗂️ Full Elderberry source code (Node.js server + React client) :contentReference[oaicite:15]{index=15}
• 🧱 Mediasoup configuration files (routers, transports)
• 📝 Setup / documentation (v1.0.4 and v2.1.0 docs) :contentReference[oaicite:16]{index=16}
• 🎨 UI components for meeting rooms, participants, controls
• 📄 This E-E-A-T HTML description for GPL/resource listings

📱 Supported Platforms

• 🖥️ Desktop browsers with WebRTC + getUserMedia (Chrome, Edge, Firefox, Safari recent) – full features. :contentReference[oaicite:17]{index=17}
• 📱 Mobile browsers (Android Chrome / iOS Safari) – A/V works, screen share depends on browser support.
• ☁️ Any VPS / cloud (DigitalOcean, Hetzner, AWS, GCP) that can expose UDP/TCP ports for Mediasoup.

🧠 Notes

License: This description assumes a GPL-style redistribution (as seen on some script archives). For commercial deployments or to get official updates/support, purchase from the original CodeCanyon/Honeyside listing. :contentReference[oaicite:18]{index=18}

Customization ideas: add JWT-based room auth, record streams server-side, integrate Stripe/billing for “paid rooms”, or embed in existing SaaS dashboards.

SEO tip: create landing pages for “self-hosted video meeting”, “Node.js WebRTC script”, and “Mediasoup React starter” to capture developer traffic.

👨‍💻 Original Developer Credit

Elderberry is originally developed and maintained by Honeyside and sold on CodeCanyon. Please retain author credit and link back to the original item when redistributing or forking. :contentReference[oaicite:19]{index=19}

Original marketplace listing

🔒 Disclaimer

This is a third-party, E-E-A-T-compliant description intended for GPL/resource sites. It is not the official sales page and does
not guarantee future updates or support. Some features (recording, TURN servers, scaling workers) require extra setup or
paid infrastructure. For mission-critical usage (telehealth, schooling, enterprise meetings), buy and follow the official documentation. :contentReference[oaicite:20]{index=20}