BBB-Streaming-Server

KO | EN

gitlite — search

#javascript #python #hacktoberfest #react #ai #typescript #llm #go #golang #android #machine-learning #rust #deep-learning #linux

BBB-Streaming-Server

(★ 11)

The BBB-Streaming-Server enables multiple BigBlueButton (BBB) meetings to be streamed to an RTMP endpoint without requiring any modifications to BBB. Docker-Images: https://hub.docker.com/r/pilos/bbb-streaming-server

BBB-Streaming-Server 최신버젼 다운로드

최종 버전 다운로드 (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# BBB-Streaming-Server

The **BBB-Streaming-Server** enables multiple BigBlueButton (BBB) meetings to be streamed to an RTMP endpoint without requiring any modifications to BBB.

A separate UI _(not included)_ or an integration into LMS platforms or BBB frontends like Greenlight or PILOS is required to use this API.

---

This Software uses BigBlueButton and is not endorsed or certified by BigBlueButton Inc. BigBlueButton and the BigBlueButton Logo are trademarks of BigBlueButton Inc.

---

## Project Architecture
This project consists of two main components:

- **Controller** – Provides an API to create and manage streaming jobs.
- **Worker** – Processes streaming jobs by joining a BBB meeting as a bot. It uses Puppeteer to control the browser and FFmpeg to stream the meeting.

## Getting Started

### Requirements
- Linux server (e.g., Ubuntu)
- Docker Compose

#### Resource Requirements
It is recommended that each worker has sufficient resources to spawn a browser to join the BBB meeting, and to encode and send a livestream video to the RTMP endpoint.

Recommendations (per livestream)
- CPUs: 2x
- Memory: 2 GB
- Bandwidth: at least 10Mbit/s upstream

The CPU, memory and bandwidth requirements also depend on the resource consumption of the BBB meeting and are therefore basically independent of streaming. With these requirements, it is possible, for example, to play movies in Full HD (approx. 30 FPS) smoothly via the video player in BBB.

### Installation

By default, this project runs in 'worker mode.' A setup consists of multiple long-running worker containers that process one or more jobs at a time. Once they complete their tasks, they remain idle until a new job arrives. There is no auto-scaling; the number of workers is fixed. You can only configure the number of workers and the maximum jobs per worker.

1. Create a new directory and place the `docker-compose.yml` file in it.
2. Adjust the `replicas` value to set the number of workers. By default, each worker can handle one streams.
3. Modify the `CONCURRENCY` environment variable if you want to allow multiple meetings per worker.
4. Start the stack by running:
   ```sh
   docker compose up -d
   ```

### Security Considerations

- By default, the API listens on `127.0.0.1:3000`. This can be modified in `docker-compose.yml`.
- The system sending API requests (e.g., a BBB frontend) must be able to reach the API.
- It is recommended to avoid directly exposing the API. Instead, use a reverse proxy to:
  - Secure the connection with SSL/TLS.
  - Implement authentication (e.g., Basic Auth).

## Environment Variables

### Controller Container
| Variable | Type | Default | Description |
|----------|------|---------|-------------|
| `REDIS_HOST` | string | `redis` | Redis host address. |
| `REDIS_PORT` | int | `6379` | Redis port number. |
| `REDIS_DB` | int | `0` | Redis database number. |
| `REDIS_PASSWORD` | string | `null` | Redis password. |
| `REDIS_USERNAME` | string | `null` | Redis username (Redis ACLs). |
| `REDIS_TLS` | boolean | `false` | Use TLS. |
| `FAILED_JOB_ATTEMPTS` | int | `3` | Number of automatic retries if a streaming job fails. |
| `KEEP_COMPLETED_JOBS_DURATION` | int | `3600` | Time (in seconds) to retain completed jobs before removal. After this, API calls to the job ID may return `404`. |
| `KEEP_FAILED_JOBS_DURATION` | int | `3600` | Time (in seconds) to retain failed jobs before removal. After this, API calls to the job ID may return `404`. |
| `MIN_WORKER_COUNT` | int | `1` | Minimum number of workers required for the health check to pass. The `/health` endpoint returns 503 if fewer workers are connected. |

### Worker Container
| Variable | Type | Default | Description |
|----------|------|---------|-------------|
| `REDIS_HOST` | string | `redis` | Redis host address. |
| `REDIS_PORT` | int | `6379` | Redis port number. |
| `REDIS_DB` | int | `0` | Redis database number. |
| `REDIS_PASSWORD` | string | `null` | Redis password. |
| `REDIS_USERNAME` | string | `null` | Redis username (Redis ACLs). |
| `REDIS_TLS` | boolean | `false` | Use TLS. |
| `CONCURRENCY` | int | `1` | Maximum number of parallel streaming jobs. |
| `FFMPEG_BITRATE` | int | `10` | Target bitrate (Mbps) for the output video stream. |
| `FFMPEG_CRF` | int | `23` | Video quality setting (lower is better; `18` is visually lossless, see FFmpeg docs). |
| `FFMPEG_METRICS_INTVL` | int | `5` | Interval (in seconds) for publishing FFmpeg metrics. |
| `FFMPEG_METRICS_AVG_LEN` | int | `10` | Length of the moving average filter for FFmpeg metrics. |
| `JSON_LOGS` | boolean | `true` | Enable logging in JSON format. |
| `CLOSE_ON_FINISH` | boolean | `false` | Only run a single job and close afterwards |

## API Documentation

The Controller exposes the following API endpoints:

- `GET /health` – Check server health and basic metrics.
- `GET /metrics` – Prometheus formatted metrics.
- `POST /` – Create a new streaming job.
- `GET /{jobId}` – Retrieve the status of a streaming job by job ID.
- `POST /{jobId}/stop` – Stop a running stream.
- `POST /{jobId}/pause` – Pause a running stream.
- `POST /{jobId}/resume` – Resume a paused stream.

For more details, refer to the [API Documentation](https://thm-health.github.io/BBB-Streaming-Server/).

## Job mode
As an alternative to the 'worker mode' you can spawn 'worker' containers on demand depending on the length of the queue. The queue length can be fetched from the `/health` and `/metrics` endpoint of the controller. You can also inspect the queue length of the redis list `bull:streams:wait`.

For such a setup you should set the `CLOSE_ON_FINISH=true` and `CONCURRENCY=1` on the worker container, so that each spawned container only handles a single job.

#### Kubernetes
You might be able to implement this approach as a KEDA [ScaledJob](https://keda.sh/docs/2.16/reference/scaledjob-spec/) with the [Redis Lists Scaler](https://keda.sh/docs/2.16/scalers/redis-lists/).

## Contributing

We welcome contributions to the **BBB-Streaming-Server** project!

### Guidelines

- Ensure your code follows the project's coding standards and conventions.
- Write clear, concise commit messages.
- Update documentation as necessary.
- Test your changes thoroughly before submitting a pull request.

Thank you for your contributions!

## License

This project is open-sourced software licensed under the LGPL license.

BBB-Streaming-Server

BBB-Streaming-Server 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

BBB-Streaming-Server

BBB-Streaming-Server 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

Download README